+1 drop hadoop 2.
On Thu, Jun 29, 2023 at 12:50 PM Xavier Léauté
wrote:
> +1, does this mean we would mark Hadoop 2 deprecated in Druid 27?
>
> Also, do we have a broader plan to remove Hadoop in general from core
> dependencies and make a an optional extension?
>
> On Tue, Jun 27, 2023 at 11:53
What about the mm-less patch? That would be nice to have in this next release?
Rahul
--- Original Message ---
On Wednesday, October 26th, 2022 at 9:13 AM, Kashif Faraz
wrote:
> Hello
>
> On the 16th of September, we released Druid 24.0.0 which was a major
> milestone in our journ
ackwards compatibility guarantees are. What I'd like us to avoid
> is to be further entrenched and bogged down in
> moving away from those dependencies by declaring a stable API.
>
> Xavier
>
> On Mon, Jun 6, 2022 at 2:45 PM rahul gidwani
> wrote:
>
> Hi Gian, this is
Druid release would have an associated Extension API version, and a
> list of supported Query API versions that users could choose between on a
> per-query basis.)
>
> Rahul, I wonder what you think about this idea? What kinds of compatibility
> are most important to you?
>
I would say that semantic versioning for me is very important for
determining compatibility between releases. Minor versions should always
adhere to being compatible with each other and a major version bump is
where you can potentially break it.
Right now calling it 24.0 is fine, but what would t
What about a 1.0 release? I think there is no backwards compatibility promised
until Druid gets to 1.0+. I think it would be really helpful to customers to
start making upgrades rollable and guaranteeing compatibility between minor
versions. Any plans for this to happen in the near future?
>
agreed, at most companies they do a vulnerability scan of the libs to see
if you have the right version.
On Mon, Dec 20, 2021 at 11:36 AM Pries, John E
wrote:
> Can I humbly recommend a quick patch to log4j2.17.0? The reason is
> security organizations don't know from application to application
What is the desired thread safety of the CompressionStrategy class? From
looking at it from an API perspective, it looks to be you:
Allocate input buffer, Allocate output buffer, compress / decompress.
The CompressionStrategyTest.testConcurrency() test if you bump the number
of threads to 100, a
