You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our lakefs server "nullpoints" with the following issue (which is concerning because our users can kill our server).
Reason seems to be empty "metadata" map in CommitCreation causes the issue.
What actually happened, including error codes if applies.
Steps to Reproduce:
LakeFS enterprise running locally in EKS
Create a import_start call with empty CommitCreation.metadata (if I remove metadata / set it to None it works)
import_creation = ImportCreation(
paths=[
ImportLocation(
type=import_type,
path=origin,
destination=prefix,
),
],
commit=CommitCreation(
message=f"CopyOp commit",
metadata={ #If i remove metadata it will work
},
allow_empty=False,
force=False,
),
force=False,
) # ImportCreation |
try:
# import data from object store
api_response : ImportCreationResponse = lakefs.import_api.import_start(repository,
branch, import_creation)
LakeFS server dies and shows this log (in our case EKS just recovers it)
What happened?
Our lakefs server "nullpoints" with the following issue (which is concerning because our users can kill our server).
Reason seems to be empty "metadata" map in CommitCreation causes the issue.
What actually happened, including error codes if applies.
Steps to Reproduce:
LakeFS server dies and shows this log (in our case EKS just recovers it)
Expected behavior
Commit includes no metadata but server does not crash
lakeFS version
1.5.0
How lakeFS is installed
No response
Affected clients
No response
Relevant log output
No response
Contact details
No response
The text was updated successfully, but these errors were encountered: