taylor schneider
10/15/2024, 7:59 PMAaron Taylor
10/17/2024, 7:03 PMDavi Gomes
10/18/2024, 3:35 PM<lakefs://data-platform-silver/main/customers/>
is not reflected in <s3://data-platform-silver/main/customers>
Jérôme Viveret
10/21/2024, 12:32 PMMatthew Butler
10/21/2024, 6:27 PMaccess_key_id
and secret_access_key
) are changing somehow without my knowledge. I'll set up LakeFS and successfully log in one day, then a few days or weeks later the creds no longer work. I'm deploying LakeFS on KubernetesAkshar Barot
10/22/2024, 7:59 AMVibhath
10/22/2024, 1:43 PMBenoit Putzeys
10/23/2024, 9:29 AMconfig.yaml
and ran the lakefs
command.
However, I get an error:
WARNING[2024-10-23T09:07:01Z]lakeFS/pkg/kv/dynamodb/store.go:199 pkg/kv/dynamodb.setupKeyValueDatabase Failed to create or detect KV table error="operation error DynamoDB: CreateTable, https response error StatusCode: 0, RequestID: , request send failed, Post \"<https://dynamodb>..<http://amazonaws.com/\|amazonaws.com/\>": dial tcp: lookup dynamodb..<http://amazonaws.com|amazonaws.com>: no such host" table_name=kvstore
INFO [2024-10-23T09:07:01Z]lakeFS/pkg/kv/dynamodb/store.go:165 pkg/kv/dynamodb.setupKeyValueDatabase.func1 Setup time table_name=kvstore took=7.253785ms
FATAL [2024-10-23T09:07:01Z]lakeFS/cmd/lakefs/cmd/run.go:159 cmd/lakefs/cmd.init.func9 Failed to open KV store error="setup failed: operation error DynamoDB: CreateTable, https response error StatusCode: 0, RequestID: , request send failed, Post \"<https://dynamodb>..<http://amazonaws.com/\|amazonaws.com/\>": dial tcp: lookup dynamodb..<http://amazonaws.com|amazonaws.com>: no such host"
I wanted to ask if you can reproduce it and help me resolve this?
Thanks in advance!Vibhath
10/23/2024, 7:39 PMBenoit Putzeys
10/24/2024, 12:12 PMmpn mbn
10/24/2024, 6:41 PMHaoming Jiang
10/24/2024, 9:37 PMmpn mbn
10/25/2024, 8:03 AMVincent Caldwell
10/26/2024, 5:13 AMRudy Cortembert
10/27/2024, 9:18 PMParth Ghinaiya
10/28/2024, 8:14 PMAndrij David
10/29/2024, 8:33 PMAndrij David
10/29/2024, 8:46 PMHaoming Jiang
10/30/2024, 1:11 AMlakefs/get_object(repository_id, reference_id, path)
, but I dont see how to write datampn mbn
10/31/2024, 12:05 PMlakectl fs rm -r <lakefs://repo/branch/A>
lakectl fs upload -r <lakefs://repo/branch/A> -s A
My question is:
How can I do this using Python lakefs package?Ocean Chang
11/06/2024, 8:12 AMauth:
remote_authenticator:
enabled: true
endpoint: <https://testendpoint.com>
default_user_group: "Developers"
ui_config:
logout_url: /logout
login_cookie_names:
- Authorization
Boris
11/07/2024, 1:01 PMOcean Chang
11/08/2024, 2:23 AMv1/auth/login
API call or the Client
from SDK. They are successful with 200. Login API call returns the token
and token_expiration
However, when subsequently trying to call /api/v1/repositories
, I m getting 401 error authenticating request
Question: Do I need to attach the login token being returned in order to make subsequent calls? If so, how?Mike Fang
11/08/2024, 7:09 PMMike Fang
11/09/2024, 1:42 AMtime="2024-11-09T01:33:57Z"
level=warning msg="Could not access storage namespace"
func="pkg/api.(*Controller).CreateRepository"
file="lakeFS/pkg/api/controller.go:2016" error="operation error S3:
PutObject, https response error StatusCode: 400, RequestID:
GV2RCD8F49KSN5K3, HostID:
P2Te8QubRyKCczc2nt/cJ3YnGfIJFDD2vJRKYoKC7JuDkMkEgN6woYVtsfChFfRhkO2HvM10uYE=,
api error InvalidRequest: Content-MD5 OR x-amz-checksum- HTTP header is
required for Put Object requests with Object Lock parameters"
reason=unknown service=api_gateway
storage_namespace="<s3://nile-data-catalog-storefangmik-406016533510-dev/test-lakefs/>"
is there something i am missing with setting up s3 wiht lakeFS? I believe the bucket permissions should be set up correctly
object lock is usualy default for s3 buckets, do they need ot be turned off now for lakefs?Akshar Barot
06/29/2025, 5:48 AMA. Katsikarelis
07/09/2025, 7:07 AMTsuHao Wang
07/10/2025, 9:54 PMGet Repository
, Get Commit
, Get Branch
, Get Object
?
2. Can we limit users to access specific commit only? On the RBAC documentation, the Get Commit is only at the repo level (arn:lakefs:fs:::repository/{repositoryId}
) but not commit level.
Thank youJason Trinidad
07/16/2025, 2:53 PMmain
branch to show just the merge commits, which would reflect the final released data for each version.
I don't see a squash functionality either on the GUI or in the docs. Does anyone know if one is available?
Thanks!Mark
07/17/2025, 2:19 PMlakectl revert
to roll back the main branch to the initial commit (with the message "Repository created"). However, this operation did not succeed. Could you advise me on how to achieve this? Are there alternative methods to revert the branch to its original state? ./lakectl branch revert <lakefs://e2e-dt/main> f66e8092ece39d11e2f3a10fab5342cb3a65cf881e237fcd4321eaedd4792dcf -y
Branch: <lakefs://e2e-dt/main>
update branch: no changes
400 Bad Request