Replies: 1 comment
-
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I'm new to the community, and congrats on the recent release and achievements!
I've been researching different systems to store my container logs, which are massive (over 1 PB per month) and semi-structured (dynamic schema). Since I lack local storage, object storage like S3 is necessary. Reads and queries are infrequent, but caching retrieved data would be ideal. Unlike Elasticsearch, scaling isn't a priority for my use case; storage and occasional querying are the main goals.
I couldn't find answers to these specific questions in the documentation, and any help would be greatly appreciated. If Doris proves suitable, I'd be happy to share my experience in a blog post.
Questions:
Table/Database Limits: I need separate tables or databases for each container log. Are there limitations on creating a large number (thousands or even 1 million) in Doris?
Iceberg on S3: The documentation mentions Doris reading/writing Iceberg in S3. Is this compatible with variants, and how does it differ from the built-in S3 cold storage system?
S3 Encryption: Is there a built-in encryption system for storing data in S3 (both cold storage and Iceberg)?
Brokers vs. S3 Solutions: How do Brokers differ from the aforementioned S3 storage solutions (cold and Iceberg)?
Caching and Dynamic Buckets: Which solution supports caching and dynamic buckets?
Benchmarks: Are there any benchmarks comparing these storage options?
selectdb Kubernetes Operator Update: The selectdb Kubernetes operator seems outdated. Is there an expected timeline for an update?
Beta Was this translation helpful? Give feedback.
All reactions