Thank you for starting this discussion, Seonggon.
I am also +1 (non-binding) for option 1: pluggable IMetaStoreClient. This
is the most realistic path for actual adoption, considering multiple
existing integrations. (Disclaimer: I work for a company that has
implemented a variant of HIVE-12679 in
ohei Okumiya wrote:
>>
>> Hi,
>>
>> I found pages removed from hive-site are not removed from
>> https://hive.apache.org/. That's probably because our CI/CD pipeline
>> doesn't remove files from the publish branch, i.e., asf-site.
>>
>> http
:
> Hi,
>
> I found pages removed from hive-site are not removed from
> https://hive.apache.org/. That's probably because our CI/CD pipeline
> doesn't remove files from the publish branch, i.e., asf-site.
>
> https://github.com/apache/hive-site/tree/asf-site
>
> We s
Hi,
I found pages removed from hive-site are not removed from
https://hive.apache.org/. That's probably because our CI/CD pipeline
doesn't remove files from the publish branch, i.e., asf-site.
https://github.com/apache/hive-site/tree/asf-site
We should solve this issue so users d
Hi Seonggon,
Thanks for being involved with the ticket, trying a PoC, and
initiating the discussion on ML.
I am currently biased toward Option 1 for some reasons.
- Option 1 likely has some existing users
- Option 1 can improve the maintainability of
SessionHiveMetaStoreClient and its family. It'
I think it's worth exposing it to developers, e.g., through the Hive
Developer Guide or elsewhere. I expect developers to be more tolerant
of hallucinations and experience some positive effects.
By the way, I'm willing to contribute to hive-site. Please raise your
hand if you are int
I wasn't aware of DeepWiki, so many thanks for sharing this tool lisoda!
>From a quick glance, the generated content for the Apache Hive repository
seems quite neat and nicely structured. I checked the results for some
other Apache projects as well and I am quite impressed with the res
+1 for Option 1: Make IMetaStoreClient pluggable
The PR addresses test flakiness. Can someone please take a look:
https://github.com/apache/hive/pull/5785
Best,
Stamatis
5 at 18:21, Simhadri G wrote:
>
> I took a deeper look at all the pages deepwiki has generated for apache hive:
> https://deepwiki.com/apache/hive/1-hive-overview
>
> The flow charts seems quite accurate and the few pages it has generated seems
> to give a good introduction
Hi all,
I would like to bring up a design discussion regarding HIVE-12679 and
HIVE-27473, which aim to support custom catalogs (such as AWS Glue, Iceberg
REST catalog, etc.).
According to the design document [1] authored by Okumin, there are two
realistic approaches to support custom catalogs
I took a deeper look at all the pages deepwiki has generated for apache
hive: https://deepwiki.com/apache/hive/1-hive-overview
The flow charts seems quite accurate and the few pages it has generated
seems to give a good introduction to hive at a very high level.
But querying Devin for an other
Hi Guys,
This sounds cool.
So I gave it a try with apache hive github repo .
Here is the link , do check it out:
https://deepwiki.com/apache/hive
But, the docs created by deepwiki do not seem to be extensive and seems to
miss a lot of information. Also, it is hallucinating quite a bit.
I
Wiki just moved to Hugo recently. I have doubts the community will start
other migration again.
In my opinion, the problem with the Hive documentation is not a wrong
platform - it is a lack of contributors.
lisoda ezt írta (időpont: 2025. ápr. 27., V, 4:32):
> Hello Team.
> I found th
Hello Team.
I found that the HBase project has started to use deepwiki to improve the
project documentation.It seems to work very well, I wonder if the hive project
can also use deepwiki to maintain project documentation?
deepwiki-hbase: https://deepwiki.com/apache/hbase
About deep wiki: https
Thanks to everyone for participating in this conversation. I’ll continue
working on removing *Arrow* from *Hive*, as we all seem to agree it’s not
worth keeping—given the lack of active use cases and the significant
footprint it leaves in the codebase.
Regards,
Laszlo Bodor
Simhadri G ezt írta
Hello,
The only use case I can recall is from when we used the HWC-LLAP mode
configured to leverage Apache Arrow. In this setup, Spark would submit
queries on Hive ACID tables through HWC. The queries were executed on LLAP,
and the data exchange between LLAP and Spark was in the Apache Arrow
Hi Laszlo,
I had a chance to talk with Apache Arrow PMCs[1] a couple of days ago
and shared my thoughts on seeking to integrate Hive with Arrow. The
timing is surprising.
Before the meetup, I looked through the only use case and didn't
understand practical use cases. So, I give +1 to remov
Hi all!
https://issues.apache.org/jira/browse/HIVE-28904
https://github.com/apache/hive/pull/5772
What do you think about removing Arrow from Hive?
As far as I can remember, that was originally introduced for the *Hive
Warehouse Connector* in its early days. Since then, other reader modes
Hi Anmol,
Short answer it's not. The 3.x line reached end-of-life on October 8, 2024, so
you'll need to upgrade your entire stack to 4.x
Regards,
Denys
Hello Apache Hive Community,
Hope you are doing well.
My use-case involves having a central Hive 4 HMS on a RDS (mysql) instance.
I also have some Hive 3 clusters (whose schema I cannot upgrade to Hive 4
yet). I am running queries from HS2 on the Hive 3 clusters which results in
HMS calls to the
The PR has two reviews but lacks a binding +1. Can a commiter take a look:
https://github.com/apache/hive/pull/5750
Best,
Stamatis
Severity: important
Affected versions:
- Apache Hive 1.1.0 before 4.0.1
Description:
Hive creates a credentials file to a temporary directory in the file system
with permissions 644 by default when the file permissions are not set
explicitly. Any unauthorized user having access to the
Severity: important
Affected versions:
- Apache Hive 2.2.0 before 4.0.0
Description:
Use of Arrays.equals() in LlapSignerImpl in Apache Hive to compare message
signatures allows attacker to forge a valid signature for an arbitrary message
byte by byte. The attacker should be an authorized
Thanks Wing Yew,
We should remove the Iceberg Hive Runtime module, but make sure that the
Iceberg Hive Metastore module tests are running against the supported(?)
Hive 2.3.10/3.1.3/4.0.1 versions. Other tests could run against
whatever Hive version they prefer
In details:
--
Let me
Can someone please review the PR:
https://github.com/apache/hive/pull/5583
https://issues.apache.org/jira/browse/HIVE-28582
Best,
Stamatis
FYI --
It looks like the built-in Hive version in the master branch of Apache
Spark is 2.3.10 (https://issues.apache.org/jira/browse/SPARK-47018), and
https://issues.apache.org/jira/browse/SPARK-44114 (upgrade built-in Hive to
3+) is an open issue.
On Mon, Jan 6, 2025 at 1:07 PM Wing Yew Poon
Hi Peter,
In Spark, you can specify the Hive version of the metastore that you want
to use. There is a configuration, spark.sql.hive.metastore.version, which
currently (as of Spark 3.5) defaults to 2.3.9, and the jars supporting this
default version are shipped with Spark as built-in. You can
Hi Manu,
> Spark has only added hive 4.0 metastore support recently for Spark 4.0[1]
and there will be conflicts
Does this mean that Spark 4.0 will always use Hive 4 code? Or it will use
Hive 2 when it is present on the classpath, but if older Hive versions are
not on the classpath then it w
>
> This basically means that we need to support every exact Hive versions
> which are used by Spark, and we need to exclude our own Hive version from
> the Spark runtime.
Firstly, upgrading from Hive 2 to Hive 4 is a huge change, and I expect
compatibility to be much better once
That sounds really interesting in a bad way :) :(
This basically means that we need to support every exact Hive versions
which are used by Spark, and we need to exclude our own Hive version from
the Spark runtime.
On Thu, Dec 19, 2024, 04:00 Manu Zhang wrote:
> Hi Peter,
>
>> I thi
Can someone please review the PR:
https://github.com/apache/hive/pull/5586
https://issues.apache.org/jira/browse/HIVE-28675
Best,
Stamatis
Severity: important
Affected versions:
- Apache Hive 1.2.0 before 4.0.0
- Apache Spark 2.0.0 before 3.0.0
- Apache Spark 3.0.0 before 3.3.4
- Apache Spark 3.4.0 before 3.4.2
- Apache Spark 3.5.0
Description:
Signing cookies is an application security feature that adds a digital
signature to
Hi all,
I believe the main factors blocking the release of version Hive 4.1.0 are the
upgrade to JDK 17 and the upgrade to Tez 0.10.5[2]. Both of these will require
some time. Ideally, it could be ready within a month, but considering the
upcoming holiday season, it might take 1-2
Hi Peter,
> I think we should make sure that the Iceberg Hive version is independent
> from the version used by Spark
I'm afraid that is not how it works currently. When Spark is deployed with
hive libraries (I suppose this is common), iceberg-spark runtime must be
compatibl
@Manu: What will be the end result? Do we have to use the same Hive version
in Iceberg as it is defined by Spark? I think we should make sure that the
Iceberg Hive version is independent from the version used by Spark
On Mon, Dec 16, 2024, 21:58 rdb...@gmail.com wrote:
> > I'm not s
ed in this 4.1.0 release. Hope to have
> other folks to share their advice.
> BTW, i want to cut the new branch 4.1.0 next week. If you want
> to include some tickets into 4.1.0, please add hive-4.1.0-must label in
> the JIRA. Some open tickets for 4.1.0 list in [1].
>
> [1
into 4.1.0, please add hive-4.1.0-must label in the JIRA.
Some open tickets for 4.1.0 list in [1].
[1]
https://issues.apache.org/jira/browse/HIVE-28669?jql=status%20in%20(Open%2C%20%22In%20Progress%22)%20AND%20labels%20%3D%20hive-4.1.0-must
Thanks,
Butao Zhang
Replied Message
> I'm not sure there's an upgrade path before Spark 4.0. Any ideas?
We can at least separate the concerns. We can remove the runtime modules
that are the main issue. If we compile against an older version of the Hive
metastore module (leaving it unchanged) that at least has a dramati
supported in 4.1.0, it would be best if we keep that promise.
> But maybe we can go ahead and release a 4.0.2 version?And then wait for
> HIVE-28665 to be merged before releasing a 4.1.0 version?
>
>
>
>
>
>
>
>
> At 2024-12-13 10:33:47, "Butao Zhang" wrot
Hi Daniel,
I'll start a vote once I get the PR ready.
Hi Ryan,
Sorry, I wasn't clear in the last email that the consensus is to upgrade
Hive metastore support.
Well, I was too optimistic about the upgrade. Spark has only added hive 4.0
metastore support recently for Spark 4.0[1] and
I agree with Butao that since the community has previously promised that jdk17
will be supported in 4.1.0, it would be best if we keep that promise.
But maybe we can go ahead and release a 4.0.2 version?And then wait for
HIVE-28665 to be merged before releasing a 4.1.0 version?
At
Oh, I think I see. The upgrade to Hive 4 is just for the Hive metastore
support? When I read the thread, I thought that we weren't going to change
the metastore. That seems reasonable to me. Sorry for the confusion.
On Fri, Dec 13, 2024 at 10:24 AM rdb...@gmail.com wrote:
> Sorry, I m
Sorry, I must have missed something. I don't think that we should upgrade
anything in Iceberg to Hive 4. Why not simply remove the Hive support
entirely? Why would anyone need Hive 4 support from Iceberg when it is
built into Hive 4?
On Thu, Dec 12, 2024 at 11:03 AM Daniel Weeks wrote:
Thanks Stamatis for your insightful suggestion! I basically agree with you, and
what you said is also what i have been thinking recently.
However, i think we've had a lot of discussion about the release of jdk17
features in version Hive 4.1.x. At some point, many community users will e
Hey Manu,
I agree with the direction here, but we should probably hold a quick
procedural vote just to confirm since this is a significant change in
support for Hive.
-Dan
On Wed, Dec 11, 2024 at 5:19 PM Manu Zhang wrote:
> Thanks all for sharing your thoughts. It looks there's a cons
> we start to address any new feedback as soon as possible.
>
> Regards
> Akshat
>
> On Thu, Dec 12, 2024 at 11:56 AM Butao Zhang wrote:
>>
>> Thanks!
>> IMO, JDK-17(HIVE-26473) should definitely be included in this release. I am
>> also watching
Akshat
On Thu, Dec 12, 2024 at 11:56 AM Butao Zhang wrote:
> Thanks!
> IMO, JDK-17(HIVE-26473) should definitely be included in this release. I
> am also watching it. Maybe we can cut the branch-4.1 at some point after
> the JDK-17 is finished.
>
>
> Thanks,
> Butao Zhang
&g
Thanks!
IMO, JDK-17(HIVE-26473) should definitely be included in this release. I am
also watching it. Maybe we can cut the branch-4.1 at some point after the
JDK-17 is finished.
Thanks,
Butao Zhang
On 2024/12/11 14:22:55 Denys Kuzmenko wrote:
> Thanks Butao!
> We'll support you
Thanks all for sharing your thoughts. It looks there's a consensus on
upgrading to Hive 4 and dropping hive-runtime.
I've submitted a PR[1] as the first step. Please help review.
1. https://github.com/apache/iceberg/pull/11750
Thanks,
Manu
On Thu, Nov 28, 2024 at 11:26 PM Shohei Okum
Thanks Butao!
We'll support you all the way.
ATM we should probably finalize the scope for the release (create new label
hive-4.1.0-must) and focus of getting those items prioritised.
There is also ongoing discussion on JDK-8 and JDK-17. Would be great if we
manage to add support for J
Hi,
We have a wiki for the release process:
https://cwiki.apache.org/confluence/display/Hive/HowToRelease
-Ayush
> On 11 Dec 2024, at 4:03 PM, Butao Zhang wrote:
>
> Hi, Denys:
>
> Good to know Hive 4.1.x is coming soon! I can be the volunteer to make
> Hive 4.
Hi, Denys:
Good to know Hive 4.1.x is coming soon! I can be the volunteer to make
Hive 4.1.x release happen. Could you share some information about the release
process? I want to learn the release process in advance.
Thanks,
Butao Zhang
On 2024/12/10 09:33:19 Denys Kuzmenko wrote
Hi All,
It's time we start prepping for the next release.
Since Hive 4.0 was cut, a number of bug-fixes, features, and performance
improvements landed in the master.
We are looking for a volunteer (Committer / PMC) to fill the role of the
next Release Manager.
Thanks,
Denys
Severity: moderate
Affected versions:
- Apache Hive 4.0.0-alpha-1 before 4.0.0
Description:
Apache Hive Metastore (HMS) uses
SerializationUtilities#deserializeObjectWithTypeInformation method when
filtering and fetching partitions that is unsafe and can lead to Remote Code
Execution (RCE
Hi Hive dev,
I found we missed the Issues Mailing List in hive-site. I think it
is necessary to add it, so some people can subscribe & receive Hive JIRA
notifications. I submitted a PR[1] to add it. Please check if it is reasonable.
BTW, i also removed the outd
Hi all,
I also prefer option 1. I have some initiatives[1] to improve
integrations between Hive and Iceberg. The current style allows us to
develop both Hive's core and HiveIcebergStorageHandler simultaneously.
That would help us enhance integrations.
- [1] https://issues.apache.org/jira/b
against Hive to
check if everything works as expected.
I'm leaning toward removing Hive 2 and 3 as well.
Kind regards,
Fokko
Op wo 27 nov 2024 om 20:05 schreef rdb...@gmail.com :
> I think that we should remove Hive 2 and Hive 3. We already agreed to
> remove Hive 2, but Hive 3 is not comp
I think that we should remove Hive 2 and Hive 3. We already agreed to
remove Hive 2, but Hive 3 is not compatible with the project anymore and is
already EOL and will not see a release to update it so that it can be
compatible. Anyone using the existing Hive 3 support should be able to
continue
> That said, it would be helpful if they continue running
> tests against the latest stable Hive releases to ensure that any
> changes don’t unintentionally break something for Hive, which would be
> beyond our control.
> I believe we should continue maintaining a Hive Iceberg run
> Let me know if the above doesn't make any sense, though!
To be honest, it doesn’t. The email feels accusatory, unfairly blaming
the Hive community for wrongdoing while portraying the Iceberg folks
as "worse" and insinuating misconduct on their part. This kind of tone
does
> Let me know if the above doesn't make any sense, though!
To be honest, it doesn’t. The email feels accusatory, unfairly blaming
the Hive community for wrongdoing while portraying the Iceberg folks
as "worse" and insinuating misconduct on their part. This kind of tone
does
Hi Gabor,
It's a bit odd to get the following feedback from the Impala folks:
"I'd like to understand the motivation why this whole replication of code
happened between Iceberg and Hive."
when you know exactly why.
FYI, we've raised our concerns multiple times to t
Hi All,
As I see there is a general opinion on not keeping the Hive code in the
Iceberg repo, but maintaining a set of tests that verifies the actual
Iceberg code against the latest Hive release. For me it would seem a bit
odd to maintain a test suite for verifying some code that is not
Hi Everyone,
Thank you, Peter, for the discussion!
I’m also leaning toward option one. However, given that Apache Iceberg is
designed to be engine-agnostic, I believe we should continue maintaining a
Hive Iceberg runtime test suite with the latest version of Hive in the
Iceberg repository. This
Hi folks,
Firstly Thanks Peter for bringing it up! I also think option 1 is
a more reasonable solution right now, as we have developed lots of advanced
iceberg features in hive repo, such as mor & cow & compaction, etc, and these
feats are coupled with Hive core code ba
For the Hive runtime, would it be feasible for the Hive community to
contribute a suite of tests to the Iceberg repo that can be run with
dependencies from the latest Hive release (Hive 4.x), and then update them
from time to time as appropriate? The purpose of this suite would be to
test
Hi Peter,
Thanks for bringing this to our attention.
>From my side, I have a say only on the code that resides in the Hive
repository. I am okay with the first approach, as we are already
following it for the most part. Whether Iceberg keeps or drops the
code shouldn’t have much impact on us.
Hi Peter,
Thanks for bringing it up!
I think that option 1 is the only viable solution here (remove the hive-runtime
from the iceberg repo). Main reason: lack of reviewers for things other than
Spark.
Note: need to double check, but I am pretty sure there is no difference between
Hive
Let's separate out the discussion of the 2 modules:
- hive-metastore - we definitely need the implementation and the tests
here, as we want to be able to progress with features like views without
waiting for a Hive release. So we need to move forward to Hive 4 now, and
keep the code in
HIVE-28519 still has open review comments, so I've merged the revert to unblock
other contributors.
Apologies for any inconvenience this may have caused
I just see that HIVE-28519: Upgrade Maven SureFire Plugin to latest version
3.5.1 is trying to fix the issue. And the Jenkins shows that it works
https://ci.hive.apache.org/job/hive-precommit/view/change-requests/job/PR-5530/lastCompletedBuild/testReport/
.
I haven't reviewed this
https://ci.hive.apache.org/job/hive-precommit/job/master/2323/testReport/
is the first build we got -60k tests.
Seems related to HIVE-28417: Bump Log4j2 to 2.24.1 to facilitate compilation of
GraalVM Native Image
We should be more careful with CVEs and dependency upgrades, they don't
Thanks Stamatis for finding this issue!
I haven't found the cause of the problem yet. I just launched a revert PR
https://github.com/apache/hive/pull/5532 to see if reverting can solve this
issue.
Thanks,
Butao Zhang
Replied Message
| From | Stamatis Zampetakis |
| Date | 11/6
Hi all,
It seems that our testing coverage has significantly dropped due to
some recent changes. Since now we are running with ~60K tests less I
would suggest holding off any commits to master till HIVE-28611 is
resolved to avoid breaking things even further.
For those PRs that appear to have
Can someone please review the PR:
https://github.com/apache/hive/pull/5497
Best,
Stamatis
find active name node I tried with below command its retiring
Thanks,
Somesh
From: Awasthi, Somesh
Sent: Friday, September 20, 2024 10:29 AM
To: u...@hive.apache.org; dev@hive.apache.org
Cc: Ayush Saxena ; d...@iceberg.apache.org
Subject: RE: Hive 4 integration to store table on S3 and AD
Thank you everyone! I'm very honored to have the chance to work on this project
and hope to contribute more to the Hive community.
Best,
Zhihua
At 2024-10-15 23:05:54, "Tanishq Chugh"
wrote:
Congratulations Zhihua Deng!
Best regards,
Tanishq
On Tue, Oct 15, 2024
Thanks everyone! I am very honored to have the chance to work on this project
and hope to contribute more to the Hive community.
Best,
Zhihua
On 2024/10/15 15:05:54 Tanishq Chugh wrote:
> Congratulations Zhihua Deng!
>
> Best regards,
> Tanishq
>
>
> On Tue, Oct 15
hanks ,
>>> >> Simhadri G
>>> >>
>>> >>
>>> >> On Sat, Oct 12, 2024, 6:48 PM Butao Zhang
>>> wrote:
>>> >>>
>>> >>> Congratulations, Zhihua!!!
>>> >>>
>>> >>> Than
,
>> >> Simhadri G
>> >>
>> >>
>> >> On Sat, Oct 12, 2024, 6:48 PM Butao Zhang wrote:
>> >>>
>> >>> Congratulations, Zhihua!!!
>> >>>
>> >>> Thanks.
>> >>>
>> >>>
t;>>
> >>> From: dev-return-161390-butaozhang1=163@hive.apache.org
> on behalf of
> Ayush Saxena
> >>> Sent: Saturday, October 12, 2024 8:55 PM
> >>> To: dev ; u...@hive.apache.org <
> u...@hive.apache.org>
> Thanks.
>>>
>>>
>>> From: dev-return-161390-butaozhang1=163@hive.apache.org
>>> on behalf of Ayush
>>> Saxena
>>> Sent: Saturday, October 12, 2024 8:55 PM
>>> To: dev ; u...@hive.apache.org
&
tulations, Zhihua!!!
>>
>> Thanks.
>>
>> --
>> *From:* dev-return-161390-butaozhang1=163@hive.apache.org
>> on behalf of
>> Ayush Saxena
>> *Sent:* Saturday, October 12, 2024 8:55 PM
>> *To:* dev ; u...@hive.apache.org <
>>
>
> [1] https://github.com/apache/hive-site/pull/17
>
t; Ayush Saxena
> *Sent:* Saturday, October 12, 2024 8:55 PM
> *To:* dev ; u...@hive.apache.org <
> u...@hive.apache.org>
> *Subject:* [ANNOUNCE] New Apache Hive PMC member : Zhihua Deng
>
> Hi All,
> It gives me immense pleasure to announce that the Apache Hive PMC has
&
Congratulations, Zhihua!!!
Thanks.
From: dev-return-161390-butaozhang1=163@hive.apache.org on behalf of Ayush Saxena Sent: Saturday, October 12, 2024 8:55 PMTo: dev ; u...@hive.apache.org Subject: [ANNOUNCE] New Apache Hive PMC member : Zhihua Deng Hi All,
It gives
Hi All,
It gives me immense pleasure to announce that the Apache Hive PMC has
voted to invite Zhihua Deng to join the PMC, and I am happy to share
that he has accepted.
This is in recognition of his ongoing contributions to the project.
Please join me in congratulating him.
Congratulations
Hi all,
Any thoughts about dropping the HCatalog's download page [1]?
[1] https://github.com/apache/hive-site/pull/17
Hi All,
The Apache Hive Community has voted to declare the 3.x release line as
End of Life.
This means no further updates or releases will be made for this release line.
We urge all Hive 3.x users to upgrade to the latest versions promptly
to benefit from new features and ongoing support.
-Ayush
>
> My negative vote here probably doesn't matter because it is a simple majority
> vote but I would like to register it nevertheless. I agree on a general plan
> to EOL Hive 3.x to focus on 4.x but it would have been better communicated
> and coordinated if we made one las
Hi Everyone,
@Lisoda ,
I have raised a PR in ranger to update the hive version from 3.1 to hive 4
and fix the HIVECONF issues.
PR: https://github.com/apache/ranger/pull/400
Please help with the reviews.
Thanks!
Simhadri G
On Tue, Oct 8, 2024 at 10:31 AM Sankar Hariappan
wrote:
> I hon
I honour community’s decision to EOL Hive 3.x which is fair based on consensus
from community.
I would like to acknowledge the efforts put in by contributors like Aman to
backport 100+ patches from master to branch-3 and reviews from Vihang, Peter,
Ayush which brought us close to 3.2 release
Thanks everyone for freely expressing their opinions. Obviously it looks
like some of the members here have strong opinions on what should be the
future of Hive 3.x and since the consensus is towards EOLing it, I am not
going to pursue this anymore.
Let’s move forward with Hive 4 and make sure we
Declaring Hive 3 as EOL is the right thing to do and as far as I see
everyone is convinced about this thus I am not planning to change/retract
my vote in the respective thread.
Based on the current situation the 3.x EOL vote will pass. I was thinking
that we could postpone the announcement for
with the issue details. Downstream we are using a version
>somewhat close to Hive-4.0 and it is fully integrated with Ranger.
>
>Another integration issue that I am familiar is HIVE-28211, that was resolved
>in a recent HIVE-4.0.1 release
>
>Regards,
>Denys
Hi @lisoda
Thanks for bringing up the Ranger issue. It would be very helpful if you could
share the JIRA with the issue details. Downstream we are using a version
somewhat close to Hive-4.0 and it is fully integrated with Ranger.
Another integration issue that I am familiar is HIVE-28211, that
projects so that they
can be supported with HIVE4.
At 2024-10-07 22:06:53, "lisoda" wrote:
As a long time user of HIVE, I would like to join this discussion.And share
some of my opinions.
Due to the bad situation of HIVE3, users are divided into two broad types:
1. Still use H
As a long time user of HIVE, I would like to join this discussion.And share
some of my opinions.
Due to the bad situation of HIVE3, users are divided into two broad types:
1. Still use HIVE1.X/2.X, and use Spark/Trino+HMS etc. to replace HIVEQL to
some extent or completely replace HIVEQL. This
utlook for Android
>
> From: vihang karajgaonkar
> Sent: Saturday, October 5, 2024 11:07:36 AM
> To: dev@hive.apache.org
> Subject: Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
>
> Thanks Stamatis!
>
> Is this wiki up to date?
> htt
1 - 100 of 17489 matches
Mail list logo
