kvlasov created HIVE-23615:
--
Summary: Null pointers should not be dereferenced
Key: HIVE-23615
URL: https://issues.apache.org/jira/browse/HIVE-23615
Project: Hive
Issue Type: Bug
Reporte
Thank you Zoltan for all this work.
I see many PRs are merged based on the new workflow already. The old
workflow generates many reports like ASF license/findbugs/checkstyle etc. I
don't see these in the new Github PR workflow. I am concerned the codebase
is going to suffer from lack of these repor
Hello Zoltan
I just got access. Not sure if this was a manual process performed by
someone on this thread or something automated, but I got an email
acknowledging.
I'm starting to close some old PRs.
Thanks.
On Thu, Jun 4, 2020 at 5:20 PM David Mollitor wrote:
> Zoltan,
>
>
> https://cwiki.a
Zoltan,
https://cwiki.apache.org/confluence/display/OPENWHISK/Accessing+Apache+GitHub+as+a+Committer
That did it for me. Thanks so much,... I'll try to remember to get this in
our Hive docs.
I still however cannot close or merge anything. I get the warning:
"Only those with write access to t
John Sherman created HIVE-23614:
---
Summary: Always pass HiveConfig to removeTempOrDuplicateFiles
Key: HIVE-23614
URL: https://issues.apache.org/jira/browse/HIVE-23614
Project: Hive
Issue Type: B
Hey Zoltan,
Thanks again for putting this together.
The original topic was dealing with a big pile of PRs. I'm starting to
work through them and pair them down a bit before we kick in something
automated (agree that we should eventually). However, I'm hampered by my
ability to not be able to me
Hey David!
> I'm trying to run the tests again and hopefully commit. Github has me
> listed as a "contributor" and lists Zoltan as a "Member of The Apache
> Software Foundation". Do you know how that list of members is managed?
I don't know; maybe you should re-link your account? You could als
Hey Zoltan,
Any idea how I can get to be a part of "member" group so I can merge some
PRs?
Thanks!
On Thu, Jun 4, 2020 at 11:40 AM Zoltan Haindrich wrote:
> Hey Stamatis!
>
> Yes, right now we should put the contributor's name into the commit
> message/etc - but in case we are using PRs that i
Hey Stamatis!
Yes, right now we should put the contributor's name into the commit message/etc - but in case we are using PRs that info is also present on the PR (or we could change the
PR label to conform to our rules)
Thank for the reference - I've just seen that there is also a "bot" to possi
László Bodor created HIVE-23613:
---
Summary: Cleanup FindBugs
Key: HIVE-23613
URL: https://issues.apache.org/jira/browse/HIVE-23613
Project: Hive
Issue Type: Bug
Reporter: László Bodo
Ádám Szita created HIVE-23612:
-
Summary: Option for HiveStrictManagedMigration to impersonate a
user for FS operations
Key: HIVE-23612
URL: https://issues.apache.org/jira/browse/HIVE-23612
Project: Hive
Pravin Sinha created HIVE-23611:
---
Summary: Mandate fully qualified absolute path for for external
table base dir during REPL operation
Key: HIVE-23611
URL: https://issues.apache.org/jira/browse/HIVE-23611
Chen LT created HIVE-23610:
--
Summary: HiveQueryResultSet#next() throw read timeout when using
hikari for rdbms
Key: HIVE-23610
URL: https://issues.apache.org/jira/browse/HIVE-23610
Project: Hive
Is
Gopal Vijayaraghavan created HIVE-23609:
---
Summary: SemiJoin: Relax big table size check for self-joins
Key: HIVE-23609
URL: https://issues.apache.org/jira/browse/HIVE-23609
Project: Hive
14 matches
Mail list logo
