Reviewers and assignees of PRs

Hey all! I'm happy to see that (I guess) everyone is using the PR based stuff without issues - there are still some flaky stuff from time-to-time; but I feel that patches go in faster - and I have a feeling we have more reviewes going on as well - which is awesome! I've read a bit about

Re: HCatalog tests create test output inside source code folders fails rat

Hey Jagat! On 6/18/20 6:20 AM, Jagat Singh wrote: I can raise PR for the annoyance I faced. Cool, that would be great! I am not sure what is the best end action we want to after checking that the working tree is clean or not, do you see that we just display the message in Gradle or actually

Re: HIVE building on ARM

Hello Chinna, The hudson-jobadmin privilege can be granted by PMC chairs. I don't know if there is any particular policy in Hive on who should have this privilege so I guess you should request it from Ashutosh. Best, Stamatis On Thu, Jun 18, 2020 at 12:05 PM Zoltan Haindrich wrote: > Hey

Re: Reviewers and assignees of PRs

Hey Panos! On 6/18/20 11:54 AM, Panos Garefalakis wrote: My only suggestion would be to make reviewing per package/label instead of files. This will make the process a bit more clear. we could use path globs to select the files - so it could match on packages as well I've not really used it

Re: HIVE building on ARM

Hey Chinna! On 6/18/20 11:43 AM, Chinna Rao Lalam wrote: As you said, migrating this job to the new ci-hadoop instance looks good as Hadoop also shares the same armN slaves. Sounds great! I am able to login the new ci-hadoop instance with Apache LDAP credentials, but i am not able to see

Re: HIVE building on ARM

Hi Zoltan, As you said, migrating this job to the new ci-hadoop instance looks good as Hadoop also shares the same armN slaves. I am able to login the new ci-hadoop instance with Apache LDAP credentials, but i am not able to see the job creation option. Should I request access or the process for

Re: Reviewers and assignees of PRs

Hey Zoltan, Thanks for doing this! This is definitely a step towards the right direction. My only suggestion would be to make reviewing per package/label instead of files. This will make the process a bit more clear. I recently bumped into this GitHub action that lets you automatically label PRs

[jira] [Created] (HIVE-23723) Limit operator pushdown through LOJ

Attila Magyar created HIVE-23723: Summary: Limit operator pushdown through LOJ Key: HIVE-23723 URL: https://issues.apache.org/jira/browse/HIVE-23723 Project: Hive Issue Type: Improvement

Some tests started hanging recently

Hey all, Since yesterday some tests started to hang - most frequently TestCrudCompactorOnTez or TestMmCompactorOnTez but I've seen a replication test as well - so I don't think its limited to those 2 tests. I was not able to figure out what have caused this - my current guess is that somehow

[jira] [Created] (HIVE-23724) Hive ACID Lock conflicts not getting resolved correctly.

Aditya Shah created HIVE-23724: -- Summary: Hive ACID Lock conflicts not getting resolved correctly. Key: HIVE-23724 URL: https://issues.apache.org/jira/browse/HIVE-23724 Project: Hive Issue

Re: Some tests started hanging recently

Hello Zoltan, I was not expecting to hear this for my first PR :( I will also try to re-run the tests locally on my system and report back to you. Thanks, Jagat Singh On Fri, 19 Jun 2020 at 00:30, Zoltan Haindrich wrote: > Hey all, > > Since yesterday some tests started to hang - most

Re: Reviewers and assignees of PRs

Hello Zoltan, One thing which needs improvement is updating of Hive Contributors wiki with whatever process happens on Github and Build server-side. The current confluence is silent on what to expect when we create a PR as a contributor, who will review, what will build system do? Where to look