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
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/
The text was updated successfully, but these errors were encountered:
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.
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 emptyand write
bucket-name/directory-path/.parseable.json
and of course all data should be insidebucket-name/directory-path/
The text was updated successfully, but these errors were encountered: