• Tal Sofer

    Tal Sofer

    7 months ago
    @Ariel Shaqed (Scolnicov) which hadoopfs method did you find that allows scalar property lookup?
    Tal Sofer
    Ariel Shaqed (Scolnicov)
    3 replies
    Copy to Clipboard
  • Marius Dieckmann

    Marius Dieckmann

    7 months ago
    hey, i am currently building a data management system, with a self-made data backend similar to yours. I am currently considering switchting to lakefs as data backend and add my own functionality on top. I do however have a question: Did you ever consider to provide support for cockroachdb as an alternative to postgres?
    Marius Dieckmann
    Oz Katz
    3 replies
    Copy to Clipboard
  • Itai David

    Itai David

    7 months ago
    Hello all, New PR is up for review - https://github.com/treeverse/lakeFS/pull/2968 TL;DR - there is an efficiency issue when looking for a best common ancestor, as part of diff The search algorithm was (possibly) going over the same commits again and again, causing the process to take much longer than needed This PR diminishes this behaviour, while (hopefully) maintaining the same outcome Please, feel free to review. All comments are welcome 🙂
    Itai David
    Ariel Shaqed (Scolnicov)
    +2
    8 replies
    Copy to Clipboard
  • Adi Polak

    Adi Polak

    6 months ago
    Heya Axolotls :levitating-lakefs: I am looking for a way to improve lakeFS documentation. One of the criteria is a reference tool. For example, when updating a specific API, it will alert us on a tutorial that uses this API that requires us to update it as well. Are you familiar with such a tool? any suggestions? Also, which documentation needs improvement asap? 💡
    Adi Polak
    t
    +1
    5 replies
    Copy to Clipboard
  • n

    Niro

    6 months ago
    Hi guys, I've been looking at branch naming in the lakeFS repository and noticed that many branches are not created according to the naming conventions under the contributing doc:
    4. If you're adding new functionality, create a new branch named feature/<DESCRIPTIVE NAME>
    5. If you're fixing a bug, create a new branch named fix/<DESCRIPTIVE NAME>-<ISSUE NUMBER>
    Maybe it's good to open this topic to discussion and understand if the requirement is important and relevant and to strictly enforce it. Otherwise maybe we should remove this requirement altogether / define a new one that makes more sense?
    n
    Barak Amar
    +1
    12 replies
    Copy to Clipboard
  • Barak Amar

    Barak Amar

    6 months ago
    In order to enable posting proposal and enable on-going work. Suggest to write them down under 'design/proposal/'. The work on the proposal and the on going changes will be done though PRs. Proposal can be closed and discard, accepted and committed to the main branch, or rejected. Rejected proposal will be moved into 'design/proposal/rejected'. Let me know what you think on the proposal proposal, to improve the current PR based solution.
    Barak Amar
    n
    4 replies
    Copy to Clipboard
  • n

    Niro

    6 months ago
    Question: What is the reason for the creation_date under the user API to be in Epoch time? Isn't it better to provide it to the user in human readable format?
    n
    1 replies
    Copy to Clipboard
  • Tal Sofer

    Tal Sofer

    6 months ago
    A naming dilemma I’ll be more than happy to get your input on - We are about to open a new repo for RouterFileSystem and looking for an appealing and clear name for it. So far we have: • hadoop-router-fs • fs-link • router-fs What is your suggestion??:help_lakefs::help_lakefs::help_lakefs::help_lakefs::help_lakefs::help_lakefs::help_lakefs::help_lakefs:
    Tal Sofer
    Ariel Shaqed (Scolnicov)
    2 replies
    Copy to Clipboard
  • Barak Amar

    Barak Amar

    6 months ago
    Go 1.18 just released - https://go.dev/doc/go1.18 🥳
    Barak Amar
    Oz Katz
    2 replies
    Copy to Clipboard
  • Ariel Shaqed (Scolnicov)

    Ariel Shaqed (Scolnicov)

    6 months ago
    Ariel Shaqed (Scolnicov)
    1 replies
    Copy to Clipboard