Re: [VOTE] Mark Hive 3.x as EOL

[Akshat m]

+1 (non binding) for EOL of Hive 3.x

Thanks
Akshat


On Wed, 2 Oct 2024 at 5:17 PM, Butao Zhang  wrote:

> +1 (non binding)
>
> Thanks.
>
> --
> *From:* dev-return-161361-butaozhang1=163@hive.apache.org
>  on behalf of
> Krisztian Kasa 
> *Sent:* Wednesday, October 2, 2024 7:31 PM
> *To:* dev 
> *Subject:* Re: [VOTE] Mark Hive 3.x as EOL
>
> +1 (Binding)
>
> Regards,
> Krisztian
>
> On Wed, Oct 2, 2024 at 12:01 PM Marta Kuczora
>  wrote:
>
>> +1 (Binding)
>>
>> Best regards,
>> Marta
>>
>> On Tue, Oct 1, 2024 at 6:11 PM Ayush Saxena  wrote:
>>
>>> Hi All,
>>> Following several discussions, this is the formal thread to mark the
>>> Hive 3.x release line as End of Life (EOL).
>>>
>>> Marking a release line as EOL means there will be no further releases
>>> for this version. However, it does not affect any existing users who
>>> can continue using it as they have been.
>>>
>>> The Vote runs a minimum of 7 days, Release management is by Lazy
>>> Majority requires more +1s than -1s
>>>
>>> I will start with my +1 (Binding)
>>>
>>> -Ayush
>>>
>>
> Thanks.
>

Re: Move to JDK-11

[Akshat m]

Hi Butao,

It won’t be feasible to support both JDK 8 and JDK 17 in the same Hive
version due to compatibility issues and behavior changes, as detailed in
the PR. The internal changes in JDK implementations have made this
challenging. Additionally, many other libraries maintain separate versions
for JDK 17+ and JDK 8 support.

To align with this approach, I suggest we continue with Hive 4 supporting
JDK 8. Once the JDK 17 PR is merged, we could plan a separate release that
specifically targets JDK 17+ support. This would ensure that Hive stays
up-to-date while maintaining stability across different environments.

Would love to hear your thoughts or any additional suggestions the
community might have!

Regards

Akshat



On Wed, Aug 28, 2024 at 8:00 AM Butao Zhang  wrote:

> Good job! Thanks everyone who put effort into the JDK upgrading. That's a
> big good news for Apache Hive community!
> Just a question: Given that many people are still using the lower jdk8
> version. Do we consider to keeping compatibility with lower jdk8 version?
>
>
> Thanks,
> Butao Zhang
> ---- Replied Message 
> From Akshat m 
> Date 8/27/2024 23:12
> To dev 
> Cc kokila narayanan,
> Raghav
> Aggarwal,
> Ayush Saxena,
> tanishq chugh,
> 
> 
> Subject Re: Move to JDK-11
>
> Hi everyone,
>
> I’m excited to share that after months of dedicated work, we’ve finally
> achieved a passing PR[1] for running *Apache Hive on JDK 17*!
>
> This was a challenging task, requiring to address various compatibility
> issues and ensure our comprehensive test suite passed without a hitch.
>
> Thanks Kokila and Tanishq for joining me in the initiative and Raghav for
> contributing fix for the errorProne issue, and thanks to Attila, Ayush and
> other Hive PMC members for their guidance in the initiative
>
> It’s been a real team effort, and I’m grateful for the collaboration and
> support from everyone involved.
>
> I’d appreciate it if you could take some time to review the PR. Community
> feedback is really important to make this happen.
>
> The PR #5404 addresses the integration of Apache Hive with JDK 17,
> introducing a range of changes aimed at ensuring compatibility and
> improving the codebase. Here’s a detailed breakdown:
>
> 1. Core Code Adjustments:
>
>- Compatibility Fixes: Various parts of the Hive codebase have been
> modified to ensure they work seamlessly with JDK 17. This includes
> addressing language or API changes that JDK 17 introduces.
>
>- Reflection and Modules: Adjustments related to how Hive interacts
> with Java's reflection API, which has stricter module system rules in JDK
> 17.
>
> 2. Dependency Management:
>
>- Version Upgrades: Several third-party dependencies have been updated
> to versions that are compatible with JDK 17. This is critical because older
> versions of some libraries may not work properly or might use deprecated
> features removed in JDK 17.
>
>- Data nucleus upgrade: To ensure compatibility with Java 17, we
> upgraded DataNucleus to version 6.x. This upgrade, however, introduced an
> issue with Hive schema creation. The issue stems from a commit in
> DataNucleus[2] that alters the handling of primary key column names by
> enclosing them in double quotes. This change caused conflicts during Hive
> schema generation. As an interim solution, we implemented a patched
> DataNucleus-rdbms module to address the issue in Hive. The necessary fix is
> now included in the DataNucleus repository[3]. Once DataNucleus 6.0.8 is
> officially released, we will upgrade to this version and remove the
> temporary patched module.
>
>  - Dependency Cleanup: Unused or outdated dependencies were removed,
> reducing potential conflicts and simplifying the build process.
>
> 3. Testing Enhancements:
>
>  - Test Suite Updates: The PR includes updates to Hive’s test suite to
> ensure all tests pass under JDK 17. This likely involved modifying tests
> that needed adjustments to align with JDK 17’s behaviour.
>
>  - New Tests: New tests may have been added to cover areas where JDK 17
> introduced new features or changes that could impact Hive.
>
> 4. Compatibility Checks:
>
>  - JDK Version Verification: A new compatibility check has been introduced
> to verify the JDK version at runtime. This ensures that Hive is running on
> an appropriate JDK version, preventing unexpected errors or behaviour due
> to version mismatches.
>
> 5. Build Updates:
>
>  - Build System Tweaks: The PR likely includes changes to the Maven build
> configuration to accommodate JDK 17, ensuring that the build process is
> smooth and compatible.
>
> Overall, this PR is a comprehensive effort to bring Apache Hive up to date
> with the lates

Re: Move to JDK-11

[Akshat m]

Hi everyone,

I’m excited to share that after months of dedicated work, we’ve finally
achieved a passing PR[1] for running *Apache Hive on JDK 17*!

This was a challenging task, requiring to address various compatibility
issues and ensure our comprehensive test suite passed without a hitch.

Thanks Kokila and Tanishq for joining me in the initiative and Raghav for
contributing fix for the errorProne issue, and thanks to Attila, Ayush and
other Hive PMC members for their guidance in the initiative

It’s been a real team effort, and I’m grateful for the collaboration and
support from everyone involved.

I’d appreciate it if you could take some time to review the PR. Community
feedback is really important to make this happen.

The PR #5404 addresses the integration of Apache Hive with JDK 17,
introducing a range of changes aimed at ensuring compatibility and
improving the codebase. Here’s a detailed breakdown:

1. Core Code Adjustments:

   - Compatibility Fixes: Various parts of the Hive codebase have been
modified to ensure they work seamlessly with JDK 17. This includes
addressing language or API changes that JDK 17 introduces.

   - Reflection and Modules: Adjustments related to how Hive interacts with
Java's reflection API, which has stricter module system rules in JDK 17.

2. Dependency Management:

   - Version Upgrades: Several third-party dependencies have been updated
to versions that are compatible with JDK 17. This is critical because older
versions of some libraries may not work properly or might use deprecated
features removed in JDK 17.

   - Data nucleus upgrade: To ensure compatibility with Java 17, we
upgraded DataNucleus to version 6.x. This upgrade, however, introduced an
issue with Hive schema creation. The issue stems from a commit in
DataNucleus[2] that alters the handling of primary key column names by
enclosing them in double quotes. This change caused conflicts during Hive
schema generation. As an interim solution, we implemented a patched
DataNucleus-rdbms module to address the issue in Hive. The necessary fix is
now included in the DataNucleus repository[3]. Once DataNucleus 6.0.8 is
officially released, we will upgrade to this version and remove the
temporary patched module.

 - Dependency Cleanup: Unused or outdated dependencies were removed,
reducing potential conflicts and simplifying the build process.

3. Testing Enhancements:

 - Test Suite Updates: The PR includes updates to Hive’s test suite to
ensure all tests pass under JDK 17. This likely involved modifying tests
that needed adjustments to align with JDK 17’s behaviour.

 - New Tests: New tests may have been added to cover areas where JDK 17
introduced new features or changes that could impact Hive.

4. Compatibility Checks:

 - JDK Version Verification: A new compatibility check has been introduced
to verify the JDK version at runtime. This ensures that Hive is running on
an appropriate JDK version, preventing unexpected errors or behaviour due
to version mismatches.

5. Build Updates:

 - Build System Tweaks: The PR likely includes changes to the Maven build
configuration to accommodate JDK 17, ensuring that the build process is
smooth and compatible.

Overall, this PR is a comprehensive effort to bring Apache Hive up to date
with the latest Java platform, ensuring long-term maintainability and
performance improvements.

As the next steps, we’ll be focusing on further sanity checks and extensive
testing to make sure everything functions smoothly. Community involvement
in this process will be crucial, so please do share any issues or feedback
as you test the changes.

I’m looking forward to seeing the benefits this will bring to our community
and users.


[1] https://github.com/apache/hive/pull/5404

[2]
https://github.com/datanucleus/datanucleus-rdbms/commit/b99df3c803862f9e9feacc7891461bcb21160b38

[3]
https://github.com/datanucleus/datanucleus-rdbms/commit/b99df3c803862f9e9feacc7891461bcb21160b38


Best regards,

Akshat Mathur


On Tue, 11 Jul 2023 at 2:25 PM, Attila Turoczy
 wrote:

> Returning to this topic, I kindly request those who would like to advocate
> for the continued support of JDK8 to please share their reasoning and
> insights with us. Your input and perspective are greatly appreciated!
> Thank you.
>
> -Attila
>
> On Fri, Jun 2, 2023 at 12:43 PM Attila Turoczy 
> wrote:
>
> > Hi All,
> >
> > I know my opinion might not be the most popular, but I advocate for
> using*
> > JDK 17*. Here's why:
> >
> > Let's consider a scenario where a customer wants to use the latest
> version
> > of Apache Hive. They would typically install it locally or on a small
> > cluster. In 2023, is it realistic to assume that this customer won't be
> > able to install JDK 17 on their cluster? Even in large enterprises, it
> > should be feasible to install an LTS JDK, especially considering the
> > widespread adoption of cloud computing. Sungwoo Park's measurements also
> > support this recommendation to go with JDK 17. It outpe

Re: [ANNOUNCE] New Committer: Stephen Carlin

[Akshat m]

Congratulations Stephen !

Regards
Akshat

On Thu, Jul 18, 2024 at 8:07 AM kokila narayanan <
kokilanarayana...@gmail.com> wrote:

> Congratulations Stephen !!
>
> Regards,
> Kokila N
>
> On Thu, 18 Jul, 2024, 07:57 Naresh P R,  wrote:
>
>> Congratulations Stephen !!!
>> —-
>> Regards,
>> Naresh P R
>>
>> On Wed, Jul 17, 2024 at 5:21 AM Stamatis Zampetakis 
>> wrote:
>>
>>> Hi All,
>>>
>>> Apache Hive's Project Management Committee (PMC) has invited Stephen
>>> Carlin to become a committer, and we are pleased to announce that he
>>> has accepted.
>>>
>>> Steve has been contributing to the project since 2019. He has improved
>>> many aspects of the project notably the query compiler and the
>>> cost-based optimizer enhancing performance and fixing multiple bugs.
>>>
>>> Stephen, welcome, thank you for your contributions, and we look forward
>>> to your further interactions with the community!
>>>
>>> Please review the guidelines for new committers [1] and take
>>> additional actions as needed.
>>>
>>> Stamatis Zampetakis (on behalf of the Apache Calcite PMC)
>>>
>>> [1] https://cwiki.apache.org/confluence/display/Hive/HowToCommit
>>>
>>

Re: Re: [ANNOUNCE] New Committer: Simhadri Govindappa

[Akshat m]

Congratulations Simhadri!, very well deserved

On Fri, Apr 19, 2024 at 3:37 PM Simhadri G  wrote:

> Thanks again everyone :)
>
> On Fri, Apr 19, 2024, 2:15 AM Rajesh Balamohan 
> wrote:
>
>> Congratulations Simhadri. :)
>>
>> ~Rajesh.B
>>
>> On Fri, Apr 19, 2024 at 2:02 AM Aman Sinha  wrote:
>>
>>> Congrats Simhadri !
>>>
>>> On Thu, Apr 18, 2024 at 12:25 PM Naveen Gangam
>>>  wrote:
>>>
 Congrats Simhadri. Looking forward to many more contributions in the
 future.

 On Thu, Apr 18, 2024 at 12:25 PM Sai Hemanth Gantasala
  wrote:

> Congratulations Simhadri 🎉 well deserved
>
> On Thu, Apr 18, 2024 at 8:41 AM Pau Tallada  wrote:
>
>> Congratulations
>>
>> Missatge de Alessandro Solimando 
>> del dia dj., 18 d’abr. 2024 a les 17:40:
>>
>>> Great news, Simhadri, very well deserved!
>>>
>>> On Thu, 18 Apr 2024 at 15:07, Simhadri G 
>>> wrote:
>>>
 Thanks everyone!
 I really appreciate it, it means a lot to me :)
 The Apache Hive project and its community have truly inspired me .
 I'm grateful for the chance to contribute to such a remarkable project.

 Thanks!
 Simhadri Govindappa

 On Thu, Apr 18, 2024 at 6:18 PM Sankar Hariappan
  wrote:

> Congrats Simhadri!
>
>
>
> -Sankar
>
>
>
> *From:* Butao Zhang 
> *Sent:* Thursday, April 18, 2024 5:39 PM
> *To:* u...@hive.apache.org; dev 
> *Subject:* [EXTERNAL] Re: [ANNOUNCE] New Committer: Simhadri
> Govindappa
>
>
>
> You don't often get email from butaozha...@163.com. Learn why
> this is important 
>
> Congratulations Simhadri !!!
>
>
>
> Thanks.
>
>
> --
>
> *发件人**:* user-return-28075-butaozhang1=163@hive.apache.org <
> user-return-28075-butaozhang1=163@hive.apache.org> 代表 Ayush
> Saxena 
> *发送时间**:* 星期四, 四月 18, 2024 7:50 下午
> *收件人**:* dev ; u...@hive.apache.org <
> u...@hive.apache.org>
> *主题**:* [ANNOUNCE] New Committer: Simhadri Govindappa
>
>
>
> Hi All,
>
> Apache Hive's Project Management Committee (PMC) has invited
> Simhadri Govindappa to become a committer, and we are pleased to 
> announce
> that he has accepted.
>
>
>
> Please join me in congratulating him, Congratulations Simhadri,
> Welcome aboard!!!
>
>
>
> -Ayush Saxena
>
> (On behalf of Apache Hive PMC)
>

>>
>> --
>> --
>> Pau Tallada Crespí
>> Departament de Serveis
>> Port d'Informació Científica (PIC)
>> Tel: +34 93 170 2729
>> --
>>
>>

Re: Force coding style in hive precommit

[Akshat m]

+1, We do have a documentation round it as well:
https://cwiki.apache.org/confluence/display/Hive/HowToContribute#HowToContribute-CodingConventions
so it makes sense to enforce it as well.

Right now we have a small section around this in documentation, We can also
expand this to a new page and add more Java practices to it as well which
are followed in the project while we are at this, Will be a great addition
to Hive 4 documentation, I can pick it up.

I suggest we add this style check as a pre-commit git hook as well, so it
is enforced when the author is committing locally as well, this can save
the wait time for pre-commit failure in the PR for the author to realise
the styling issues, ideally this should be taken care of with the ide style
configuration but in case we miss it this would error out while
committing the changes.

Regards,
Akshat

On Sat, Jan 6, 2024 at 10:17 AM László Bodor 
wrote:

> Hi All!
>
> What do you think about forcing coding style in Hive precommit?
>
> I remember, back in the old days, precommit printed some warnings in case
> some coding style (formatting, indentation, naming convention, etc.)
> problems were found in the patch, now it's simply not used, I guess since
> we're using GitHub PRs.
>
> For example: I remember I simply approved a PR a few months ago which
> LGTM, and later just realized it's full of 4-spaces indentation, which is
> wrong if we assume that code should be formatted according to the style
> definition here:
> https://github.com/apache/hive/blob/master/dev-support/eclipse-styles.xml
>
> I have just attached an example of Tez PR to open minds and start a
> conversation.
>
> Regards,
> Laszlo Bodor
>
>

Re: Help with Docker Apache/Hive metastore using mysql remote database

[Akshat m]

Hi,

You can download it from here:
https://repo1.maven.org/maven2/mysql/mysql-connector-java/8.0.29/mysql-connector-java-8.0.29.jar

Regards,
Akshat

On Thu, Dec 21, 2023 at 1:40 AM Sanjay Gupta  wrote:

> There is no mysql driver file in following repo
> https://repo1.maven.org/maven2/org
>
> On Mon, Dec 18, 2023 at 3:10 AM Simhadri G  wrote:
> >
> > We can modify the Dockerfile to wget the necessary driver and copy it to
> /opt/hive/lib/ .  This should make it work. The diff is attached below:
> >
> >
> > diff --git a/packaging/src/docker/Dockerfile
> b/packaging/src/docker/Dockerfile
> > --- a/packaging/src/docker/Dockerfile (revision
> dceaf810b32fc266e3e657fdaefcd4507f2191b5)
> > +++ b/packaging/src/docker/Dockerfile (date 1702897518609)
> > @@ -80,6 +80,9 @@
> >
> >  ENV PATH=$HIVE_HOME/bin:$HADOOP_HOME/bin:$PATH
> >
> > +RUN wget
> https://repo1.maven.org/maven2/org/postgresql/postgresql/42.5.1/postgresql-42.5.1.jar
> > +RUN cp /postgresql-42.5.1.jar /opt/hive/lib/
> > +
> >  COPY entrypoint.sh /
> >  COPY conf $HIVE_HOME/conf
> >  RUN chmod +x /entrypoint.sh
> >
> > On Mon, Dec 18, 2023, 12:59 PM Ayush Saxena  wrote:
> >>
> >> I think the similar problem is being chased as part of
> >> https://github.com/apache/hive/pull/4948
> >>
> >> On Mon, 18 Dec 2023 at 09:48, Sanjay Gupta  wrote:
> >> >
> >> >
> >> >
> >> >
> >> > Issue with Docker container using mysql RDBMS ( Failed to load driver)
> >> >
> >> > https://hub.docker.com/r/apache/hive
> >> >
> >> > According to readme
> >> >
> >> > Launch Standalone Metastore With External RDBMS
> (Postgres/Oracle/MySql/MsSql)
> >> >
> >> > I want to use MySQL
> >> >
> >> > I tried com.mysql.jdbc.Driver or com.mysql.cj.jdbc.Driver
> >> >
> >> > docker run -it -d -p 9083:9083 --env SERVICE_NAME=metastore
> --add-host=host.docker.internal:host-gateway \
> >> >  --env DB_DRIVER=mysql \
> >> >  --env
> SERVICE_OPTS="-Djavax.jdo.option.ConnectionDriverName=com.mysql.jdbc.Driver
> -Djavax.jdo.option.ConnectionURL=jdbc:mysql://host.docker.internal:3306/hive?createDatabaseIfNotExist=true
> -Djavax.jdo.option.ConnectionUserName=hive
> -Djavax.jdo.option.ConnectionPassword=password" \
> >> >  --mount source=warehouse,target=/opt/hive/data/warehouse \
> >> >  --name metastore-standalone apache/hive:${HIVE_VERSION}
> >> >
> >> >
> >> > docker run -it -d -p 9083:9083 --env SERVICE_NAME=metastore
> --add-host=host.docker.internal:host-gateway \
> >> >  --env DB_DRIVER=mysql \
> >> >  --env
> SERVICE_OPTS="-Djavax.jdo.option.ConnectionDriverName=com.mysql.cj.jdbc.Driver
> -Djavax.jdo.option.ConnectionURL=jdbc:mysql://host.docker.internal:3306/hive?createDatabaseIfNotExist=true
> -Djavax.jdo.option.ConnectionUserName=hive
> -Djavax.jdo.option.ConnectionPassword=password" \
> >> >  --mount source=warehouse,target=/opt/hive/data/warehouse \
> >> >  --name metastore-standalone apache/hive:${HIVE_VERSION}
> >> >
> >> > Docker logs shows this for both drivers ( same error )
> >> >
> >> > docker logs f3
> >> > + : mysql
> >> > + SKIP_SCHEMA_INIT=false
> >> > + export HIVE_CONF_DIR=/opt/hive/conf
> >> > + HIVE_CONF_DIR=/opt/hive/conf
> >> > + '[' -d '' ']'
> >> > + export 'HADOOP_CLIENT_OPTS= -Xmx1G
> -Djavax.jdo.option.ConnectionDriverName=com.mysql.cj.jdbc.Driver
> -Djavax.jdo.option.ConnectionURL=jdbc:mysql://host.docker.internal:3306/hive?createDatabaseIfNotExist=true
> -Djavax.jdo.option.ConnectionUserName=hive
> -Djavax.jdo.option.ConnectionPassword=hive'
> >> > + HADOOP_CLIENT_OPTS=' -Xmx1G
> -Djavax.jdo.option.ConnectionDriverName=com.mysql.cj.jdbc.Driver
> -Djavax.jdo.option.ConnectionURL=jdbc:mysql://host.docker.internal:3306/hive?createDatabaseIfNotExist=true
> -Djavax.jdo.option.ConnectionUserName=hive
> -Djavax.jdo.option.ConnectionPassword=hive'
> >> > + [[ false == \f\a\l\s\e ]]
> >> > + initialize_hive
> >> > + /opt/hive/bin/schematool -dbType mysql -initSchema
> >> > SLF4J: Class path contains multiple SLF4J bindings.
> >> > SLF4J: Found binding in
> [jar:file:/opt/hive/lib/log4j-slf4j-impl-2.17.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> >> > SLF4J: Found binding in
> [jar:file:/opt/hadoop/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> >> > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> >> > SLF4J: Actual binding is of type
> [org.apache.logging.slf4j.Log4jLoggerFactory]
> >> > Metastore connection URL:
> jdbc:mysql://host.docker.internal:3306/hive?createDatabaseIfNotExist=true
> >> > Metastore Connection Driver : com.mysql.cj.jdbc.Driver
> >> > Metastore connection User: hive
> >> > org.apache.hadoop.hive.metastore.HiveMetaException: Failed to load
> driver
> >> > Underlying cause: java.lang.ClassNotFoundException :
> com.mysql.cj.jdbc.Driver
> >> > Use --verbose for detailed stacktrace.
> >> > *** schemaTool failed ***
> >> > + '[' 1 -eq 0 ']'
> >> > + echo 'Schema initialization failed!'
> >> > Schema initialization failed!
> >> > + exit 1
>

Re: ci execute too long, 13h..., branch2

[Akshat m]

Hi,

We do have a timeout mechanism in place, for branch-2 it is set to 24hrs:
https://github.com/apache/hive/blob/659aa5d94ffc15696c4729694ba68a77a58c2074/Jenkinsfile#L70

I couldn't find any recent PRs with test passed label for branch-2 to
compare an appropriate time for this job completion, you can update/reduce
the value here based on your PR if the tests passes,
You can also play around with the number of split here:
https://github.com/apache/hive/blob/659aa5d94ffc15696c4729694ba68a77a58c2074/Jenkinsfile#L25
to get a get to a more appropriate timeout, for master we have it at 12hr
with 22 splits.

Thanks
Akshat

On Tue, Dec 19, 2023 at 9:23 AM 高雄  wrote:

> hi,
> http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-4955/1/pipeline/623/
> split-16 is running more than 13h, but no test fail on this split. Is it
> have timeout mechanism or other mechanism to stop it.

Re: [help] Jira account for first contribute

[Akshat m]

Hi,

Apache has initiated a serve service process, where you can request for a
jira account.
Please submit your details via this portal:
https://selfserve.apache.org/jira-account.html

Thanks

On Mon, Dec 18, 2023 at 1:18 PM 高雄  wrote:

> Hi，i fixed a bug about udaf used over window, like this, select
> row_number2() over(), local. so i need a Jira account. please help.

[Twitter] Blog on Hive's Data Federation Capabilities

[Akshat m]

Delve into the world of data federation with Apache Hive in this blog. Explore
the essence of data federation, uncover Hive's capabilities, and learn
about its supported integrations. Don't miss out on the insights:
https://akshatmat.medium.com/data-federation-with-apache-hive-74b3bc5fb72
#DataFederation #ApacheHive #DataAnalytics

Regards,
Akshat Mathur

Query regarding Accumulo Support

[Akshat m]

Hi everyone

I am writing to inquire about the current state of support for Accumulo in
Hive, particularly with regard to its testing and stability. Furthermore, I
would like to discuss the possibility of deprecating Accumulo in an
upcoming release(4.x) unless there are specific plans or use cases that
warrant its continued support.

Few questions I have are: Has it been actively maintained and tested to
ensure compatibility with recent changes in Hive and Accumulo? Are there
any known issues or limitations that users should be aware of? It would be
helpful to understand the level of support and reliability we can expect
when working with Hive and Accumulo integration.

Considering the rapid development on both Hive and accumulo side and the
need to focus development efforts on widely adopted and actively used
components, I believe it is essential to periodically reassess the
inclusion of such features. In this context, I would like to discuss the
potential deprecation of Accumulo in a future Hive release.

If Accumulo lacks widespread adoption or if its integration with Hive is
not sufficiently tested and stable, deprecating it could streamline
development efforts and allow for increased focus on other critical areas
and stable Hive release. However, I understand that there might be specific
use cases or plans that necessitate its continued support. If this is the
case, I would appreciate a brief understanding of such scenarios.

Please share your insights, recommendations, and any pertinent information
regarding the same.

I look forward to hearing views on this.
Regards,
Akshat Mathur

Re: [ANNOUNCE] New committer for Apache Hive: Alessandro Solimando

[Akshat m]

Congratulations Alessandro :)

Regards,
Akshat Mathur

On Thu, Feb 9, 2023 at 12:11 PM Mahesh Raju Somalaraju <
maheshra...@cloudera.com> wrote:

> Congratulations Alessandro !!
>
> -Mahesh Raju S
>
> On Thu, Feb 9, 2023 at 1:31 AM Naveen Gangam  wrote:
>
>> The Project Management Committee (PMC) for Apache Hive has invited
>> Alessandro Solimando (asolimando) to become a committer and is pleased
>> to announce that he has accepted.
>>
>> Contributions from Alessandro:
>> He has authored 30 patches for Hive, 18 for Apache Calcite and has
>> done many code reviews for other contributors. Vast experience and
>> knowledge in SQL Compiler and Optimization. His most recent work was
>> added support for histogram-based column stats in Hive.
>>
>> https://issues.apache.org/jira/issues/?filter=12352498
>>
>> Being a committer enables easier contribution to the project since
>> there is no need to go via the patch submission process. This should
>> enable better productivity.A PMC member helps manage and guide the
>> direction of the project.
>>
>> Congratulations
>> Hive PMC
>>
>

Re: [ANNOUNCE] New committer for Apache Hive: Laszlo Vegh

[Akshat m]

Congratulations Laszlo, Very well deserved :)

Regards,
Akshat Mathur

On Tue, Feb 7, 2023 at 9:08 PM Sai Hemanth Gantasala
 wrote:

> Congratulations Laszlo Vegh, Great work on the compaction stuff!!
>
> Thanks,
> Sai.
>
> On Tue, Feb 7, 2023 at 4:24 AM Naveen Gangam  wrote:
>
> > The Project Management Committee (PMC) for Apache Hive has invited Laszlo
> > Vegh (veghlaci05) to become a committer and we are pleased
> > to announce that he has accepted.
> >
> > Contributions from Laszlo:
> >
> > He has authored 25 patches. Significant contributions to stabilization of
> > ACID compaction. Helped review other patches as well.
> >
> >
> >
> https://github.com/apache/hive/pulls?q=is%3Amerged+is%3Apr+author%3Aveghlaci05
> >
> > Being a committer enables easier contribution to the project since there
> > is no need to go via the patch submission process. This should enable
> > better productivity.A PMC member helps manage and guide the direction of
> > the project.
> >
> > Congratulations
> > Hive PMC
> >
>

Re: [ANNOUNCE] New PMC Member: Krisztian Kasa

[Akshat m]

Congratulations Krisztian :)

Regards,
Akshat

On Mon, Jan 30, 2023 at 10:23 PM Alessandro Solimando <
alessandro.solima...@gmail.com> wrote:

> Congratulations Krisztian, very well deserved! :)
>
> On Mon, 30 Jan 2023 at 17:34, László Bodor 
> wrote:
>
>> Yay! Very well deserved. Krisztian has a broad knowledge of Hive and an
>> extremely deep level of experience with the compiler itself (which is a
>> huge beast we all know), looking forward to seeing further contributions!
>>
>> Naveen Gangam  ezt írta (időpont: 2023.
>> jan. 30., H, 17:23):
>>
>>> Hello Hive Community,
>>> Apache Hive PMC is pleased to announce that Krisztian Kasa (username:
>>> krisztiankasa) has accepted the Apache Hive PMC's invitation to become
>>> PMC
>>> Member, and is now our newest PMC member. Please join me in
>>> congratulating
>>> Krisztian !!!
>>>
>>> He has been an active member in the hive community across many aspects of
>>> the project. Many thanks to Krisztian for all the contributions he has
>>> made
>>> and looking forward to many more future contributions in the expanded
>>> role.
>>>
>>> https://github.com/apache/hive/commits?author=kasakrisz
>>>
>>> * 162 commits in master
>>> * 124 reviews in master
>>> * Reported 159 JIRAS
>>>
>>> Cheers,
>>> Naveen (on behalf of Hive PMC)
>>>
>>

Re: [ANNOUNCE] New PMC Member: Laszlo Bodor

[Akshat m]

Congratulations Laszlo

Regards,
Akshat

On Sat, Jan 28, 2023 at 3:03 AM Naveen Gangam 
wrote:

> Hello Hive Community,
> Apache Hive PMC is pleased to announce that Laszlo Bodor
> (username:abstractdog) has accepted the Apache Hive PMC's invitation to
> become PMC Member, and is now our newest PMC member. Please join me in
> congratulating Laszlo !!!
>
> He has been an active member in the hive community across many aspects of
> the project. Many thanks to Laszlo for all the contributions he has made
> and looking forward to many more future contributions in the expanded role.
>
> https://github.com/apache/hive/commits?author=abstractdog
>
> * 96 commits in master [2]
> * 66 reviews in master [3]
> * Reported 163 JIRAS [6]
>
> Cheers,
> Naveen (on behalf of Hive PMC)
>

Re: [EXTERNAL] [ANNOUNCE] New PMC Member: Stamatis Zampetakis

[Akshat m]

Congratulations Stamatis :)

On Sun, 15 Jan 2023 at 12:51 AM, Sai Hemanth Gantasala
 wrote:

> Congratulations Stamatis, Very well deserved!!!
>
> On Fri, Jan 13, 2023 at 10:57 AM Chris Nauroth 
> wrote:
>
> > Congratulations, Stamatis!
> >
> > Chris Nauroth
> >
> >
> > On Fri, Jan 13, 2023 at 10:46 AM Simhadri G 
> wrote:
> >
> > > Congratulations Stamatis!
> > >
> > > On Sat, 14 Jan 2023, 00:12 Sankar Hariappan via user, <
> > > u...@hive.apache.org>
> > > wrote:
> > >
> > > > Congrats Stamatis! Well deserved one 😊
> > > >
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > Sankar
> > > >
> > > >
> > > >
> > > > *From:* Naveen Gangam 
> > > > *Sent:* Saturday, January 14, 2023 12:03 AM
> > > > *To:* dev ; u...@hive.apache.org
> > > > *Cc:* zabe...@apache.org
> > > > *Subject:* [EXTERNAL] [ANNOUNCE] New PMC Member: Stamatis Zampetakis
> > > >
> > > >
> > > >
> > > > Hello Hive Community,
> > > >
> > > > Apache Hive PMC is pleased to announce that Stamatis Zampetakis has
> > > > accepted the Apache Hive PMC's invitation to become PMC Member, and
> is
> > > now
> > > > our newest PMC member. Please join me in congratulating Stamatis !!!
> > > >
> > > >
> > > >
> > > > He has been an active member in the hive community across many
> aspects
> > of
> > > > the project. Many thanks to Stamatis for all the contributions he has
> > > made
> > > > and looking forward to many more future contributions in the expanded
> > > role.
> > > >
> > > >
> > > >
> > > > Cheers,
> > > >
> > > > Naveen (on behalf of Hive PMC)
> > > >
> > >
> >
>