Simhadri, thank you for sharing the information.
Thanks,
Cheng Pan
Hi Cheng Pan,
There is long running Hive mail thread discussing this here:
https://lists.apache.org/thread/sxcrcf4v9j630tl9domp0bn4m33bdq0s
On Thu, Apr 18, 2024 at 11:15 AM Cheng Pan wrote:
> Hi Ayush,
>
> > Hive is already in discussion of marking Hive-2.x EOL, so at very best
> we would have
Hi Ayush,
> Hive is already in discussion of marking Hive-2.x EOL, so at very best we
> would have one release and immediately after that we will announce it EOL
Does the discussion happen in public? Is there an ETA for the final release of
branch-2.3?
Thanks,
Cheng Pan
> On Apr 17, 2024, at
Thanx Cheng Pan for sharing the pointers, Do you have any list of issues or
pointers on what are the challenges for Spark to move to a higher Hive
version? I know upgrading libraries is quite challenging but it
is inevitable.
Hive is already in discussion of marking Hive-2.x EOL, so at very best w
> … we are exploring ways to get Spark move from 2.3.9 to 4.0, Our initial
> hunch is that it would be quite challenging without a hive-exec slim jar …
It should be challenging to upgrade Spark’s built-in Hive version. Actually, we
already did lots of work on branch-2.3 which focuses on CVE redu
There is a JIRA ticket[1] that tracks "upgrading built-in Hive to 3+”
BTW, regarding HMS API used by Spark, the Hive 2.3.9 client is compatible with
HMS from 2.0 to 4.0, while the upcoming Hive 2.3.10 client should be compatible
with HMS from 1.2 to 4.0, if we decide to upgrade the built-in Hive
I've observed the hive-exec:3.x version, where in the 3.1.0 version, I
found the core classifier library. When we can expect a similar core
classifier library in the 4.1.0 version.
On Wed, Apr 17, 2024 at 4:14 AM Ayush Saxena wrote:
> Some can't be relocated, it is pretty challenging to relocat
Some can't be relocated, it is pretty challenging to relocate them, one I
remember is calcite, I tried that here:
https://issues.apache.org/jira/browse/HIVE-23772 & it didn't work, I am not
sure if things have changed now.
Relocated dependencies shouldn't be problematic I believe, having jars
shad
isn't this as simple to solve as relocating joda (or what causes problems
in general)? I cannot recall when and why we removed the core jar, and I'm
not against it, but I feel that relocating something that is already shaded
in the uber jar is much easier
looks like we shade a lot:
https://github.
When can we expect the core jar for 4.0.0 version.
On Tue, Apr 16, 2024 at 4:57 PM Denys Kuzmenko wrote:
> Hi Ravi,
>
> hive-exec is the uber jar, the same thing is done in Hive-3.x. We are
> considering restoring the hive-core jar that only has classes from ql
>
> On 2024/04/16 06:24:20 Mergu R
Hi Ravi,
hive-exec is the uber jar, the same thing is done in Hive-3.x. We are
considering restoring the hive-core jar that only has classes from ql
On 2024/04/16 06:24:20 Mergu Ravi wrote:
> Hi Hive Team,
>
> I'm currently using the Hive 4.0.0 libraries and facing an issue with the
> hive-exec
Hi Hive Team,
I'm currently using the Hive 4.0.0 libraries and facing an issue with the
hive-exec:4.0.0 library. It seems that the Joda-Time library is bundled
within it, preventing me from excluding it and using my existing Joda-Time
library. Could you please provide insight into why this bundlin
Hi Hive Team,
I'm currently using the Hive 4.0.0 libraries and facing an issue with the
hive-exec:4.0.0 library. It seems that the Joda-Time library is bundled
within it, preventing me from excluding it and using my existing Joda-Time
library. Could you please provide insight into why this bundlin
13 matches
Mail list logo
