Skip to content

Conversation

@gurjotkaur20
Copy link
Contributor

Fixes #574 .

Description

  • Added custom error when S3 bucket is not found.
  • Write metdata in staging only when remote metadata write is successful.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 10, 2024

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@gurjotkaur20
Copy link
Contributor Author

I have read the CLA Document and I hereby sign the CLA

nitisht added a commit to parseablehq/.github that referenced this pull request Jan 10, 2024
@nitisht nitisht merged commit 26b2ec0 into parseablehq:main Jan 10, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jan 10, 2024
@gurjotkaur20 gurjotkaur20 deleted the fix-server-start-error-with-s3 branch February 7, 2024 00:17
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Parseable server start error with s3-store with incorrect/invalid bucket name

2 participants