Re: Hive 4.0 interview/podcast
It is a really valuable interview!!! Thanks Rich and Stamatis!!! Thanks, Butao Zhang Replied Message | From | Ayush Saxena | | Date | 6/11/2024 21:57 | | To | , | | Subject | Re: Hive 4.0 interview/podcast | Hey Guys, I just watched the interview - It's awesome. Big thanx to Rich & Stamatis for putting this together!!! -Ayush On Tue, 11 Jun 2024 at 18:38, Rich Bowen wrote: Hi, folks. Congratulations on the release of Hive 4.0. I've just published an interview with Stamatis Zampetakis, and it's live at https://youtu.be/7HX2MieyzW4 (video) and at https://wp.me/p8gHED-41k (just the audio). Thanks, Stamatis! It was good talking with you. --Rich
Re: [VOTE] Mark Hive 2.x EOL
+1 Thanks Butao Zhang Replied Message | From | Ayush Saxena | | Date | 5/10/2024 08:45 | | To | dev | | Subject | [VOTE] Mark Hive 2.x EOL | Hi All, Following the discussion at [1]. Starting the official vote thread to mark Hive 2.x release line as EOL. Marking a release lines as EOL means there won't be any further release made for that release line I will start with my +1 -Ayush [1] https://lists.apache.org/thread/91wk3oy1qo953md7941ojg2q97ofsl2d
Re: [ANNOUNCE] New Committer: Simhadri Govindappa
Congratulations Simhadri !!! Thanks. 发件人: user-return-28075-butaozhang1=163@hive.apache.org 代表 Ayush Saxena 发送时间: 星期四, 四月 18, 2024 7:50 下午收件人: dev ; 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)
Re: [Blog] Apache Hive 4.0 Release blog for ASF M & P
Good job Ayush! Hope this can make more people know that Apache Hive 4.0 is really ready to be used! Thanks, Butao Zhang Replied Message | From | Ayush Saxena | | Date | 4/5/2024 19:55 | | To | dev | | Subject | [Blog] Apache Hive 4.0 Release blog for ASF M & P | Hi All, Have been talking to the ASF M & P team and they recongonise the 4.0 release is a big milestone for our project. They are happy to have an entry for us in the their news column, ex: https://news.apache.org/foundation/entry/apache-software-foundation-announces-apache-wicket-v10 So, I along with Denys, Simhadri & tons of help from ChatGpt have prepared a draft to share with them. The draft is here: https://docs.google.com/document/d/10Zu8pHvWNDRTqn7yvYqvU4-kw3Q1TXo7mGo5m5fUP2Y/edit If you have some feedback or concerns, please share with us. If you want some improvements or removals, let us know here & we will do that, or if you need write access to this page, just let me know. If nobody objects, I plan to send this to the team by next week Tuesday -Ayush
Re: [ANNOUNCE] Apache Hive 4.0.0 Released
I'm thrilled to see the official release of Apache Hive 4.0.0, marking another milestone in the development of the Hive community. I want to extend my gratitude to all the partners in the community for their hard work. Also special thanks to Denys for your diligent code reviews and efforts in completing the version release process, which I deeply admire. Wishing the Apache Hive community continued growth and success. Keep up the great work! Thanks, Butao Zhang Replied Message | From | Stamatis Zampetakis | | Date | 4/2/2024 16:39 | | To | | | Cc | u...@hive.apache.org | | Subject | Re: [ANNOUNCE] Apache Hive 4.0.0 Released | The new Apache Hive 4.0.0 release brings roughly 5K new commits (since Apache Hive 3.1.3) and it's probably the biggest release so far in the history of the project. The numbers clearly show that this is a collective effort that wouldn't be possible without a strong community and many volunteers along the years. Many thanks to everyone involved! A special mention to Denys who went above and beyond his role of release manager triaging release blockers, reviewing and fixing many of those tickets that were blocking us for the past few months. Best, Stamatis On Sun, Mar 31, 2024 at 2:54 PM Battula, Brahma Reddy wrote: Thank you for your hard work and dedication in releasing Apache Hive version 4.0.0. Congratulations to the entire team on this achievement. Keep up the great work! Does this consider as GA.? And Looks we need to update in the following location also.? https://hive.apache.org/general/downloads/ From: Denys Kuzmenko Date: Saturday, March 30, 2024 at 00:07 To: u...@hive.apache.org , dev@hive.apache.org Subject: [ANNOUNCE] Apache Hive 4.0.0 Released The Apache Hive team is proud to announce the release of Apache Hive version 4.0.0. The Apache Hive (TM) data warehouse software facilitates querying and managing large datasets residing in distributed storage. Built on top of Apache Hadoop (TM), it provides, among others: * Tools to enable easy data extract/transform/load (ETL) * A mechanism to impose structure on a variety of data formats * Access to files stored either directly in Apache HDFS (TM) or in other data storage systems such as Apache HBase (TM) * Query execution via Apache Hadoop MapReduce, Apache Tez and Apache Spark frameworks. (MapReduce is deprecated, and Spark has been removed so the text needs to be modified depending on the release version) For Hive release details and downloads, please visit: https://hive.apache.org/downloads.html Hive 4.0.0 Release Notes are available here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343343=Text=12310843 We would like to thank the many contributors who made this release possible. Regards, The Apache Hive Team
Re: [VOTE] Release Apache Hive 4.0.0 (Release Candidate 0)
+1 (non-binding) I checked: [x] Build the 4.0.0 source code successfully: mvn clean package -DskipTests -Pdist -Piceberg -Pitests [x] Deploy and start the binary tar against Hadoop3.3.6 & Tez0.10.3 successfully. [x] Run some test SQLs, such as create acid table/ iceberg table, and do some basic/acid operations (insert/delete/update) [x] Enable Ranger authorization plugin, do some db/tbl permission check. Thanks Denys for driving the release. I'm excited to see the official upcoming release of version Hive 4.0.0! Replied Message | From | Denys Kuzmenko | | Date | 3/26/2024 15:26 | | To | | | Subject | [VOTE] Release Apache Hive 4.0.0 (Release Candidate 0) | Hi Everyone, We would like to thank everyone who has contributed to the project and request the Hive PMC members to review and vote on this new release candidate. Apache Hive 4.0.0 RC-0 artifacts are available here:* https://people.apache.org/~dkuzmenko/apache-hive-4.0.0-rc0/ The checksums are as follows: - 83eb88549ae88d3df6a86bb3e2526c7f4a0f21acafe21452c18071cee058c666 apache-hive-4.0.0-bin.tar.gz - 4dbc9321d245e7fd26198e5d3dff95e5f7d0673d54d0727787d72956a1bca4f5 apache-hive-4.0.0-src.tar.gz You can find the KEYS file here: * https://downloads.apache.org/hive/KEYS A staged Maven repository URL is:* https://repository.apache.org/content/repositories/orgapachehive-1127/ The git commit hash is:* https://github.com/apache/hive/commit/183f8cb41d3dbed961ffd27999876468ff06690c This corresponds to the tag: release-4.0.0-rc0 * https://github.com/apache/hive/tree/release-4.0.0-rc0 The vote is open for the next 72 hours and passes if a majority of at least three +1 PMC votes are cast. (Only PMC members have binding votes, however, other community members are encouraged to cast non-binding votes.) [ ] +1 Release this package as Apache Hive 4.0.0 [ ] +0 [ ] -1 Do not release this because... Please download, verify, and test. Regards, Denys
Re: [VOTE] Mark Hive 1.x EOL
+1 Thanks, Butao Zhang Replied Message | From | Ayush Saxena | | Date | 1/17/2024 14:15 | | To | dev | | Subject | [VOTE] Mark Hive 1.x EOL | Hi All, Following the discussion in [1], Starting an official thread to mark Hive 1.x EOL. Marking a release line EOL, means there won't be any further releases for that release line. I will start with my +1 -Ayush [1] https://lists.apache.org/thread/sxcrcf4v9j630tl9domp0bn4m33bdq0s
Re: review help
Hi gaoxiong, Thanks for you contribution! I left several minor comments, please take a look. Thanks, Butao Zhang Replied Message | From | tcgaoxiong | | Date | 1/15/2024 18:27 | | To | dev@hive.apache.org | | Subject | review help | Hi, Can anyone review this pr help? HIVE-27960. The test has passed. Thanks. gaoxiong
Re: [DISCUSS] Deprecate/Drop upgrade-acid module from 4.x
+1. I am not sure the use case of upgrade-acid module, but it seems that this module is rarely used in my world. I think maybe the first safe step is deprecating this module to let users know that this module should not be used any more. BTW, my idea tells me that this module used the old Hive2.3.3 which has some vulnerability. Should we consider upgrading this dependency to hive4?: "Dependency maven:org.apache.hive:hive-metastore:2.3.3 is vulnerable, safe version 4.0.0-alpha-2" CVE-2021-34538 7.5 Missing Authentication for Critical Function vulnerability Thanks, Butao Zhang Replied Message | From | Ayush Saxena | | Date | 1/10/2024 07:45 | | To | dev | | Subject | [DISCUSS] Deprecate/Drop upgrade-acid module from 4.x | Hi Folks, Wanted to know thoughts on removing the upgrade-acid module[1] from 4.x. The javadoc on one of the main files[2] read "This utility is designed to help with upgrading Hive 2.x to Hive 3.0". I think this is a 2.x to 3.x thing and doesn't look relevant for Hive-4.x. Checking the git log, I don't find any relevant development happening on this either. The main challenge that this brings is that it depends on legacy Hive(2.3.3) & Hadoop(2.7.2) [3], which aren't JDK-11 compliant & it blocks the way for Hive JDK-11 compile time support. Let me know your thoughts!!! -Ayush [1] https://github.com/apache/hive/tree/master/upgrade-acid [2] https://github.com/apache/hive/blob/master/upgrade-acid/pre-upgrade/src/main/java/org/apache/hadoop/hive/upgrade/acid/PreUpgradeTool.java#L86C4-L86C72 [3] https://github.com/apache/hive/blob/master/upgrade-acid/pre-upgrade/pom.xml#L38-L39
Re: Force coding style in hive precommit
+1 BTW, We have a independent checkstyle file under iceberg module https://github.com/apache/hive/tree/master/iceberg/checkstyle . I think we need to consider unifing the checkstyle in all the sub-module. Thanks, Butao Zhang Replied Message | From | Zsolt Miskolczi | | Date | 1/8/2024 16:19 | | To | | | Subject | Re: Force coding style in hive precommit | +1 In case there is an agreement about the coding style, we can prepare a tool that enforces that style at compile time. Run a tool one time to re-format all the existing code once. And turn on a compile time check. Iceberg did the same approach, they had one huge commit with almost 4k files changed and from that point, it worked well. And there are no issues about formatting. I don't think putting a warning message helps at all. Also, it should be enforced on compile time. Zsolt Kirti Ruge ezt írta (időpont: 2024. jan. 8., H, 7:20): +1 As it would improve maintainability and code reviews. Sometimes small indentation/styling issues would kill review cycle time and we can easily avoid it before requesting review. Enforcing more rules around it definitely boost guaranteeing quality. We can integrate it with git hooks. If we are going for this, I can work on getting it in place . Thanks, Kirti On 08-Jan-2024, at 11:36 AM, Akshat m wrote: +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: How to use `engine` introduced by HIVE-22046
Hi, dev Bump this thread! I just filed a ticket to track this incompatibility issues about hms column stats thrift api. I think we can fix this at its root in HMS side and then any other third components will not suffer from this issue. https://issues.apache.org/jira/browse/HIVE-27984 Thanks, Butao Zhang Replied Message | From | Okumin | | Date | 8/20/2023 18:37 | | To | | | Subject | Re: How to use `engine` introduced by HIVE-22046 | Hi Butao, Thanks for sharing your PR! I didn't find trinodb/trino-hive-apache or trinodb/hive-thrift. As mentioned in the PR, the current Thrift definitions might not be the final version, but it sounds reasonable to give information to external products since we versioned Hive 4 beta. I'm curious if anyone why we give different engine names to Hive and Impala and what are the recommended options. Thanks, Okumin On Fri, Aug 11, 2023 at 10:39 AM Butao Zhang wrote: Hi, Okumin I have encountered this issue before, and the 'validWriteIdList' is also a incompatibility parameter. I have submit a PR in trino-hive-apache repo, and you can refer to https://github.com/trinodb/trino-hive-apache/pull/43 . IIUC, the 'engine' parameter is used to differentiate between stats produced by different engines(Hive), but it seems that the downstream engines do not want to adopt the new 'engine' parameter. At present, if some engines(e.g. Trino) use the customized thrift api to interact wiht hms, it must change its thrift file to match the thrift definition of hms. BTW, maybe we can change hms thrift file to make the 'engine' parameter optional and then other customized thrift client will not have compatibility issues. Thanks, Butao Zhang Replied Message | From | Okumin | | Date | 8/10/2023 23:41 | | To | | | Subject | How to use `engine` introduced by HIVE-22046 | Hi Hive developers, I noticed HIVE-22046 introduced incompatibility to Metastore APIs while I'm testing integration between Hive 4 and other software. If I understand correctly, clients are currently required to additionally specify the engine name when they get or update column statistics. - https://issues.apache.org/jira/browse/HIVE-22046 - https://github.com/apache/hive/pull/741 For example, Trino has a feature to use column stats and it fails. Note that I am not 100% sure about Trino's implementation or behavior. ``` trino> create table hive.default.test_trino (id int); Query 20230810_152236_4_t9n6h failed: Required field 'engine' is unset! Struct:TableStatsRequest(dbName:default, tblName:test_trino, colNames:[id], engine:null) ``` I have two questions about this feature. (1) Should any engine use a unique engine name? I guess some software can store or use stats compatible with Hive. I wonder if it can reuse engine=hive in that case, or should use a different name like engine=trino. I see Impala gives a unique engine name to metastore. Taking a glance, Spark is unlikely to be using col stats of Hive directly. - https://issues.apache.org/jira/browse/IMPALA-8842 (2) Should Hive Metastore use engine=hive as a default value? If other compatible software can reuse engine=hive, it could be an option to accept requests with the old format assuming its engine is "hive" for compatibility. Or should they explicitly specify engine=hive when using Hive 4? Regards, Okumin
Flaky test testBootstrapAcidTablesDuringIncrementalWithConcurrentWrites
Hi Hive dev, I find the test testBootstrapAcidTablesDuringIncrementalWithConcurrentWrites often fails in CI. We had to rerun the total CI because of the single flaky test, and this wastes development time and CI resoures. I raised a ticket https://issues.apache.org/jira/browse/HIVE-27936 to track this flay test and found it failed in many PR tests. Also, the flaky report shows that this test is flaky, see http://ci.hive.apache.org/job/hive-flaky-check/756/testReport/. If we don't have good way to fix the flaky test, i think we should disable it. Thanks, Butao Zhang
Re: Release of Hive 4 and TPC-DS benchmark
Cool! Thank you Denys for driving this! Thanks, Butao Zhang Replied Message | From | Attila Turoczy | | Date | 11/23/2023 22:29 | | To | | | Subject | Re: Release of Hive 4 and TPC-DS benchmark | Excellent new Denys! Hive 4 is here! Can't wait :) -Attila On Thu, Nov 23, 2023 at 3:20 PM Denys Kuzmenko wrote: Update: 1. Query 2, 71: Resolved in HIVE-27006 [1]; 2. Query 97: Under review in HIVE-27269 [2]; Thanks, Seonggon for providing a reproduce qfile. 3. Query 14: Reported in HIVE-24167 [3]; set hive.optimize.cte.materialize.threshold to -1 by default in Hive 4 and fix it in the next versions 4. HIVE-26986 [4] is a performance improvement that is nice to have, but not a blocker for the release. Be advised, next week we plan to cut 4.0.0 release branch from master and start testing. Thanks, Denys [1] https://issues.apache.org/jira/browse/HIVE-27006 [2] https://issues.apache.org/jira/browse/HIVE-27269 [3] https://issues.apache.org/jira/browse/HIVE-24167 [4] https://issues.apache.org/jira/browse/HIVE-26986
Re: [ANNOUNCE] New committer: Butao Zhang (zhangbutao)
Thank you to the Hive community for this honor. I will continue to contribute to the community with my efforts. Thanks all! Thanks, Butao Zhang Replied Message | From | Ayush Saxena | | Date | 11/21/2023 15:02 | | To | dev , , Butao Zhang | | Subject | [ANNOUNCE] New committer: Butao Zhang (zhangbutao) | Hi All, Apache Hive's Project Management Committee (PMC) has invited Butao Zhang to become a committer, and we are pleased to announce that he has accepted. Butao Zhang welcome, thank you for your contributions, and we look forward to your further interactions with the community! Ayush Saxena (On behalf of Apache Hive PMC)
Re: How to use `engine` introduced by HIVE-22046
Hi, Okumin I have encountered this issue before, and the 'validWriteIdList' is also a incompatibility parameter. I have submit a PR in trino-hive-apache repo, and you can refer to https://github.com/trinodb/trino-hive-apache/pull/43 . IIUC, the 'engine' parameter is used to differentiate between stats produced by different engines(Hive), but it seems that the downstream engines do not want to adopt the new 'engine' parameter. At present, if some engines(e.g. Trino) use the customized thrift api to interact wiht hms, it must change its thrift file to match the thrift definition of hms. BTW, maybe we can change hms thrift file to make the 'engine' parameter optional and then other customized thrift client will not have compatibility issues. Thanks, Butao Zhang Replied Message | From | Okumin | | Date | 8/10/2023 23:41 | | To | | | Subject | How to use `engine` introduced by HIVE-22046 | Hi Hive developers, I noticed HIVE-22046 introduced incompatibility to Metastore APIs while I'm testing integration between Hive 4 and other software. If I understand correctly, clients are currently required to additionally specify the engine name when they get or update column statistics. - https://issues.apache.org/jira/browse/HIVE-22046 - https://github.com/apache/hive/pull/741 For example, Trino has a feature to use column stats and it fails. Note that I am not 100% sure about Trino's implementation or behavior. ``` trino> create table hive.default.test_trino (id int); Query 20230810_152236_4_t9n6h failed: Required field 'engine' is unset! Struct:TableStatsRequest(dbName:default, tblName:test_trino, colNames:[id], engine:null) ``` I have two questions about this feature. (1) Should any engine use a unique engine name? I guess some software can store or use stats compatible with Hive. I wonder if it can reuse engine=hive in that case, or should use a different name like engine=trino. I see Impala gives a unique engine name to metastore. Taking a glance, Spark is unlikely to be using col stats of Hive directly. - https://issues.apache.org/jira/browse/IMPALA-8842 (2) Should Hive Metastore use engine=hive as a default value? If other compatible software can reuse engine=hive, it could be an option to accept requests with the old format assuming its engine is "hive" for compatibility. Or should they explicitly specify engine=hive when using Hive 4? Regards, Okumin
Re: [DISCUSS] Automatic rerunning of failed tests in Hive Pre-commit
+1. I often have to rerun whole pre-commit job due to individual unstable test, ant it is too time-consuming. It would be much better if we can set maven config to retry automatically. Thanks, Butao Zhang Replied Message | From | r12 t45 | | Date | 6/8/2023 14:52 | | To | | | Subject | [DISCUSS] Automatic rerunning of failed tests in Hive Pre-commit | Hi All, It often happens that Hive unit tests fail during pre-commit which requires rerunning the whole pre-commit job and creates hours of delays. What if we set Maven config to retry failed tests automatically X times? There is "rerunFailingTestsCount" property in maven-surefire-plugin which can be used for that. I would like to hear the feedback and if it is positive I could open a JIRA ticket and work on it. Thanks, Dmitriy
Re: Move to JDK-11
Thanks Ayush for driving this! Good to know that Hive is getting ready for newer JDK. From my opinon, if we have more community energy to put into it, we can support both JDK-11 and JDK-17 like Spark[1]. If we have to make a choice between a JDK-11 and JDK-17, i would like to choose the relatively new version JDK-17, meanwhile, we should maintain compatibility with jdk8, as JDK-8 is still widely used in most big data platforms. Thanks, Butao Zhang [1]https://issues.apache.org/jira/browse/SPARK-33772 Replied Message | From | Ayush Saxena | | Date | 5/31/2023 18:39 | | To | dev | | Subject | Move to JDK-11 | Hi Everyone, Want to pull in the attention of folks towards moving to JDK-11 compile time support in Hive. There was a ticket in the past [1] which talks about it and If I could decode it right, it was blocked because the Hadoop version used by Hive didn't had JDK-11 runtime support, But with [2] in we have upgraded the Hadoop version, so that problem is sorted out. I couldn't even see any unresolved tickets in the blocked state either. I quickly tried* a mvn clean install -DskipTests -Piceberg -Pitests -Dmaven.javadoc.skip=true And no surprises it failed with some weird exceptions towards the end. But I think that should be solvable. So, Questions? - What do folks think about this? Should we put in some effort towards JDK-11 - Should we support both JDK-11 & JDK-8? - Ditch JDK-11 and directly shoot for JDK-17? Let me know your thoughts, In case anyone has some experience in this area and have tried something in the context, feel free to share or may be if someone has any potential action plan or so -Ayush [1] https://issues.apache.org/jira/browse/HIVE-22415 [2] https://issues.apache.org/jira/browse/HIVE-24484 * changed the maven.compiler.source & maven.compiler.target to 11
Re: Request to join Hive slack channel
Thanks Ayush. The invitation is valid. I have joined the hive slack channel. Thanks, Butao Zhang Replied Message | From | Soumyakanti Das | | Date | 5/19/2023 14:43 | | To | | | Subject | Re: Request to join Hive slack channel | Hey Ayush, Please add me to the channel as well. My email is soumyakanti.das...@gmail.com Thanks! On Thu, May 18, 2023 at 23:34 Ayush Saxena wrote: Sure Sungwoo, I will add you as well. Butao Zhang was added to the channel, I can see him in the list of members and I received a notification as well that his account has been approved by the infra team, I think I am not the only one to approve, it has to be approved by Infra as well. Let me wait for sometime if there are other non-committer interested as well in joining the #hive slack channel, so I can submit the request all together, approving one-one request might piss off Infra folks :-) -Ayush On Fri, 19 May 2023 at 11:44, Sungwoo Park wrote: I am sorry for spamming -- My email address is: glap...@gmail.com Thanks, --- Sungwoo Park On Fri, May 19, 2023 at 3:11 PM Sungwoo Park wrote: If non-committers can join the slack channel, I would like to join, too. An invitation will be appreciated very much (glapa...@gmail.com). Thanks, --- Sungwoo Park On Fri, May 19, 2023 at 2:49 PM Butao Zhang wrote: Hi, Hive dev I just saw this updated page: https://cwiki.apache.org/confluence/display/Hive/HowToCommit. It seems we individual can request to join the slack channel. If that is possible, I want to join the slack, please give me a invitation, Thanks. My Gmail address: butaozha...@gmail.com Thanks, Butao Zhang
Request to join Hive slack channel
Hi, Hive dev I just saw this updated page: https://cwiki.apache.org/confluence/display/Hive/HowToCommit. It seems we individual can request to join the slack channel. If that is possible, I want to join the slack, please give me a invitation, Thanks. My Gmail address: butaozha...@gmail.com Thanks, Butao Zhang
Re: [ANNOUNCE] New PMC Member: Laszlo Bodor
Congratulations Laszlo Bodor !!! Thanks, Butao Zhang Replied Message | From | Alessandro Solimando | | Date | 1/28/2023 06:23 | | To | | | Cc | , | | Subject | Re: [ANNOUNCE] New PMC Member: Laszlo Bodor | Congratulations Laszlo, very well deserved, thanks for all your hard work. Best regards, Alessandro On Fri, 27 Jan 2023 at 22:33, 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] Re: [ANNOUNCE] New PMC Member: Ayush Saxena
Congratulations Ayush ! Replied Message | From | Jan Fili | | Date | 12/20/2022 18:38 | | To | | | Subject | Re: [EXTERNAL] Re: [ANNOUNCE] New PMC Member: Ayush Saxena | gratz! Am Di., 20. Dez. 2022 um 11:09 Uhr schrieb Aasha : Congratulations Ayush. Very well deserved On 20-Dec-2022, at 3:36 PM, Pau Tallada wrote: Congratulations! Missatge de Mayank Singh del dia dt., 20 de des. 2022 a les 9:01: Congratulations Ayush 拾 On Tue, 20 Dec, 2022, 1:19 pm Stamatis Zampetakis, wrote: Congrats Ayush! Very well deserved! Thanks for all the hard work that you are putting for the project and always being there when people ask for help. Best, Stamatis On Tue, Dec 20, 2022 at 7:51 AM Sankar Hariappan via user wrote: Congrats Ayush! Thanks, Sankar From: Simhadri G Sent: Tuesday, December 20, 2022 12:16 PM To: u...@hive.apache.org Cc: dev ; ayushsax...@apache.org Subject: [EXTERNAL] Re: [ANNOUNCE] New PMC Member: Ayush Saxena Congratulations Ayush On Tue, 20 Dec 2022, 06:42 Naveen Gangam, wrote: Hello Hive Community, Apache Hive PMC is pleased to announce that Ayush Saxena has accepted the Apache Hive PMC's invitation to become PMC Member, and is now our newest PMC member. Many thanks to Ayush for all the contributions he has made and looking forward to many more future contributions in the expanded role. Please join me in congratulating Ayush !!! Cheers, Naveen (on behalf of Hive PMC) -- -- Pau Tallada Crespí Departament de Serveis Port d'Informació Científica (PIC) Tel: +34 93 170 2729 --
