Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature request : permit parseable to not use a whole bucket but only a sub directory of this bucket. #310

Open
fcomte opened this issue Feb 23, 2023 · 3 comments
Assignees
Labels

Comments

@fcomte
Copy link

fcomte commented Feb 23, 2023

Parseable claim that a S3 bucket is dedicated to him.
If a bucket is not empty, there is an error at launch time.
If the bucket is empty then Parseable can start and write at location bucket-name/.parseable.json

In some context you don't have access to an entire bucket.
It would be usefull if we can configure a directory with S3.
Parseable should then check that bucket-name/directory-path/ is empty
and write bucket-name/directory-path/.parseable.json and of course all data should be inside bucket-name/directory-path/

@nitisht
Copy link
Member

nitisht commented Feb 24, 2023

Thanks @fcomte we'll take a look and get back on feasibility

@nitisht nitisht added the triage label Feb 24, 2023
@nitisht
Copy link
Member

nitisht commented Apr 20, 2023

We discussed this deeply @fcomte but looks like it will be confusing to general users. Without a dedicated bucket, it is highly possible that Parseable data gets muddled across different prefixes, additionally this will involve a considerable code change in Parseable repo.

Hence we'd like to request you if you can arrange access to a empty bucket for use with Parseable. Closing this issue for now, feel free to get back if there are further questions.

@nitisht nitisht closed this as completed Apr 20, 2023
@nitisht nitisht removed the triage label Apr 20, 2023
@nitisht nitisht reopened this Mar 22, 2024
@nitisht
Copy link
Member

nitisht commented Mar 22, 2024

We'll revisit this again. Thanks for the discussion @fcomte

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants