• Ariel Shaqed (Scolnicov)

    Ariel Shaqed (Scolnicov)

    1 year ago
    About the 8 extra bytes at the end of each LevelDB key inside a RocksDB SSTable: that's the "internal" keys, incorporating some versioning. Here's the documentation on Internal Keys.
    Ariel Shaqed (Scolnicov)
    1 replies
    Copy to Clipboard
  • Ariel Shaqed (Scolnicov)

    Ariel Shaqed (Scolnicov)

    1 year ago
    If you're having trouble pushing or doing anything GitHub really, bear in mind it is not feeling well: status.github.com. 😿
    Ariel Shaqed (Scolnicov)
    Oz Katz
    2 replies
    Copy to Clipboard
  • Ariel Shaqed (Scolnicov)

    Ariel Shaqed (Scolnicov)

    1 year ago
    Reminder: you should be using 2-factor authentication on your GitHub account. Go and do that now if that's not the case. Still here? Great! If you have no access to your phone then your printed recovery codes, stored in a safe location, may be the only way to gain access to your account from a new device. These are your ultimate fallback, so if you don't know where they are, go to https://github.com/settings/auth/recovery-codes, print out a new set, and keep it safe!
    Ariel Shaqed (Scolnicov)
    1 replies
    Copy to Clipboard
  • Yoni Augarten

    Yoni Augarten

    1 year ago
    Opened this issue regarding changing the docs to exclude the wildcard DNS record from our basic documentation instructions, to reduce friction and simplify deployment. Question to everyone: for this to work, the user will have to force path-style access, at least in some AWS clients. Considering that 2 DNS records still need to be created, and that the s3_gatway_domain parameter still needs to be specified for lakeFS, how much simpler does it actually make things?
    Yoni Augarten
    Guy Hardonag
    2 replies
    Copy to Clipboard
  • Ariel Shaqed (Scolnicov)

    Ariel Shaqed (Scolnicov)

    1 year ago
    TIL AWS added a VPC reachability analyzer: give it a source and a destination endpoint, maybe a port, hit a button, (wait a few minutes), it says if that path works... and why it doesn't!https://console.aws.amazon.com/vpc/home?region=us-east-1#ReachabilityAnalyzer:
    Ariel Shaqed (Scolnicov)
    1 replies
    Copy to Clipboard
  • Ariel Shaqed (Scolnicov)

    Ariel Shaqed (Scolnicov)

    1 year ago
    I've been testing https://github.com/treeverse/lakeFS/pull/2335 on our user metadata simulation (thanks, @Yoni Augarten!).... It seems to work! Details on the issue. Any objections to me pulling it? @Oz Katz @Guy Hardonag
    Ariel Shaqed (Scolnicov)
    1 replies
    Copy to Clipboard
  • mishraprafful

    mishraprafful

    1 year ago
    Hey, I wish to add a PR for some quick documentation bug but am unable to create a branch as I get a 403, is it possible for someone to add me as a contributor maybe ? My GitHub username is @mishraprafful P.S I have singed the SLA as mentioned here https://docs.lakefs.io/contributing.html
    mishraprafful
    Yoni Augarten
    +1
    7 replies
    Copy to Clipboard
  • Yoni Augarten

    Yoni Augarten

    1 year ago
    Hey all, working on designing repo-level settings in lakeFS. I'm considering using Graveler for versioning, so as to allow a discoverable history of each setting. I was wondering if anyone has thoughts about whether this is possible and how to go about it. The way I see it, if we use the same database schema as the lakeFS installation, we must create new repositories for storing the settings, but those will be visible to the user which may be strange. WDYT?
    Yoni Augarten
    Oz Katz
    4 replies
    Copy to Clipboard
  • Barak Amar

    Barak Amar

    1 year ago
    TIL; vim users (sorry neovim) -
    :smile
    Barak Amar
    Oz Katz
    2 replies
    Copy to Clipboard
  • Itai Admi

    Itai Admi

    1 year ago
    Solving bug #2397 , I think it’s clear that we want the following 2 examples to store files in the same physical location:
    <s3://bucket/prefix>
    and
    <s3://bucket/prefix/>
    . i.e. all objects stored in
    <s3://bucket/prefix/>
    But what about cases when the user provides something strange like
    <s3://bucket/prefix///>
    , should we also store it under
    <s3://bucket/prefix/>
    , or is
    <s3://bucket/prefix///>
    appropriate in this case..?
    Itai Admi
    Oz Katz
    2 replies
    Copy to Clipboard