paleolimbot opened a new issue, #48: URL: https://github.com/apache/sedona-db/issues/48
From @zhangfengcdt in https://github.com/apache/sedona-db/pull/44 : ``` // TODO: Consider registering object stores per-bucket instead of per-scheme to avoid // authentication conflicts. Currently, if a user first accesses a public S3 bucket with // aws.skip_signature=true and then tries to access a private bucket, the cached object // store will still have skip_signature enabled, preventing authentication to the private // bucket. A per-bucket registration approach would solve this by using bucket-specific // cache keys like "s3://bucket-name" instead of just "s3://". ``` (Opening an issue so that we can remember/discover this and circle back!) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
