[jira] [Resolved] (PHOENIX-5364) Run OrderByWithServerClientSpoolingDisabledIT and OrderByWithServerMemoryLimitIT in their own mini cluster.

2019-06-21 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl resolved PHOENIX-5364. Resolution: Fixed Pushed to 4.x and master. > Run OrderByWithServerClientSpoolingDisable

[jira] [Updated] (PHOENIX-5364) Run OrderByWithServerClientSpoolingDisabledIT and OrderByWithServerMemoryLimitIT in their own mini cluster.

2019-06-21 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5364: --- Summary: Run OrderByWithServerClientSpoolingDisabledIT and OrderByWithServerMemoryLimitIT i

[jira] [Updated] (PHOENIX-5364) Run OrderByWithServerClientSpoolingDisabledIT and

2019-06-21 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5364: --- Summary: Run OrderByWithServerClientSpoolingDisabledIT and (was: Tests fail "Queue Full"

[jira] [Updated] (PHOENIX-5364) Tests fail "Queue Full" only when run in parallel with other tests.

2019-06-21 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5364: --- Description: Spooling defaults to true. Yet, I see some tests failing (sometimes) with exc

[jira] [Updated] (PHOENIX-5364) Tests fail "Queue Full" only when run in parallel with other tests.

2019-06-21 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5364: --- Fix Version/s: 5.1.0 4.15.0 > Tests fail "Queue Full" only when run in p

[jira] [Assigned] (PHOENIX-5364) Tests fail "Queue Full" only when run in parallel with other tests.

2019-06-21 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reassigned PHOENIX-5364: -- Assignee: Lars Hofhansl > Tests fail "Queue Full" only when run in parallel with oth

[jira] [Updated] (PHOENIX-5364) Tests fail "Queue Full" only when run in parallel with other tests.

2019-06-21 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5364: --- Attachment: 5364.txt > Tests fail "Queue Full" only when run in parallel with other tests.

[jira] [Created] (PHOENIX-5364) Tests fail "Queue Full" only when run in parallel with other tests.

2019-06-21 Thread Lars Hofhansl (JIRA)
Lars Hofhansl created PHOENIX-5364: -- Summary: Tests fail "Queue Full" only when run in parallel with other tests. Key: PHOENIX-5364 URL: https://issues.apache.org/jira/browse/PHOENIX-5364 Project: Ph

[jira] [Updated] (PHOENIX-5359) Remove (Global-Indexing)new coprocessors in CQSI#addCoprocessors with flag(INDEX_REGION_OBSERVER_ENABLED_ATTRIB) disabled

2019-06-21 Thread Swaroopa Kadam (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam updated PHOENIX-5359: Attachment: (was: PHOENIX-5359.4.x-hbase-1.3.v1.patch) > Remove (Global-Indexing)new

[jira] [Updated] (PHOENIX-5359) Remove (Global-Indexing)new coprocessors in CQSI#addCoprocessors with flag(INDEX_REGION_OBSERVER_ENABLED_ATTRIB) disabled

2019-06-21 Thread Swaroopa Kadam (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam updated PHOENIX-5359: Attachment: (was: PHOENIX-5359.master.v1.patch) > Remove (Global-Indexing)new coproce

Re: [PHOENIX-4863: Setup Travis-CI & CodeCoverage

2019-06-21 Thread Priyank Porwal
Thanks Geoffrey for standing in my defense and Andrew for consensus suggestion! We can ignore the vote for now and continue the discussion though, which is great. Hopefully it will lead us to some next steps; and maybe consensus. I'll explore HBase's usage of Yetus. Does anyone have suggestions t

Re: [VOTE] PHOENIX-4863: Setup Travis-CI & CodeCoverage

2019-06-21 Thread Priyank Porwal
The IT do successfully start in Travis just fine, but Travis has a time limit of 50 minutes for open-source projects, and Phoenix ITs run for almost 3 hours. This limit is applied per 'job' and not to the complete cycle. I did attempt to break down Phoenix ITs into multiple jobs, but couldn't compl

Re: [VOTE] PHOENIX-4863: Setup Travis-CI & CodeCoverage

2019-06-21 Thread Andrew Purtell
It's not inappropriate but I encourage the community to try for consensus before voting. On Fri, Jun 21, 2019 at 11:07 AM Geoffrey Jacoby wrote: > Andrew, > > If the vote was inappropriate, my apologies -- it was my offline suggestion > to Priyank to call one when he felt he was ready to proceed

Re: [VOTE] PHOENIX-4863: Setup Travis-CI & CodeCoverage

2019-06-21 Thread Geoffrey Jacoby
Andrew, If the vote was inappropriate, my apologies -- it was my offline suggestion to Priyank to call one when he felt he was ready to proceed. There had been a general discussion on the list on the matter about a month ago that was generally supportive of the idea, but was preliminary and didn't

Re: [VOTE] PHOENIX-4863: Setup Travis-CI & CodeCoverage

2019-06-21 Thread Geoffrey Jacoby
I'm -0 (as the Apache voting page defines it -- "I won't get in the way, but I'd rather we didn't do this") because of the stated limitation to unit tests only. The bulk of our testing is currently through IT tests, so as a committer I wouldn't have sufficient confidence to commit a patch based sol

[jira] [Updated] (PHOENIX-5363) Phoenix parcel artifacts for CDH releases don't pass Cloudera verification tools test

2019-06-21 Thread Mehdi Salarkia (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mehdi Salarkia updated PHOENIX-5363: Description: Following instruction from Cloudera [https://github.com/cloudera/cm_ext/wi

Re: [VOTE] PHOENIX-4863: Setup Travis-CI & CodeCoverage

2019-06-21 Thread Andrew Purtell
Point of order Apache communities generally do not vote to achieve consensus. That should be a last resort. Please do not vote to make these kinds of decisions. On Fri, Jun 21, 2019 at 12:15 AM Priyank Porwal wrote: > [Converting this thread to a community vote] > > I'd like to start Travis-CI a

Re: [VOTE] PHOENIX-4863: Setup Travis-CI & CodeCoverage

2019-06-21 Thread Andrew Purtell
Travis is underpowered compared to ASF test infrastructure. Do the integration tests run there? Recommend using ASF infra and Yetus (yetus.apache.org). HBase provides a completely worked example of how to integrate and use it for precommit. On Fri, Jun 21, 2019 at 12:15 AM Priyank Porwal wrote:

Re: [VOTE] PHOENIX-4863: Setup Travis-CI & CodeCoverage

2019-06-21 Thread Josh Elser
Gotta amend this: I am -1 without the ability to successfully run all of the tests (including integration tests). Some of the chatter on made me think that ITs were actually running on Travis (which _really_ surprised me). On 6/21/19 1:35 PM, Josh Elser wrote: I am -0. I don't see value in t

Re: [VOTE] PHOENIX-4863: Setup Travis-CI & CodeCoverage

2019-06-21 Thread Josh Elser
I am -0. I don't see value in trying to integrate with an external CI system when we already have the ASF Jenkins that gives us more insight than just about any other system will give us. Integrating PreCommit jobs with Github is a question to ASF Infra and copying the PreCommit job and chec

[jira] [Updated] (PHOENIX-5363) Phoenix parcel artifacts for CDH releases don't pass Cloudera verification tools test

2019-06-21 Thread Mehdi Salarkia (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mehdi Salarkia updated PHOENIX-5363: Description: Following instruction from Cloudera [https://github.com/cloudera/cm_ext/wi

[jira] [Created] (PHOENIX-5363) Phoenix parcel artifacts for CDH releases don't pass Cloudera verification tools test

2019-06-21 Thread Mehdi Salarkia (JIRA)
Mehdi Salarkia created PHOENIX-5363: --- Summary: Phoenix parcel artifacts for CDH releases don't pass Cloudera verification tools test Key: PHOENIX-5363 URL: https://issues.apache.org/jira/browse/PHOENIX-5363

[jira] [Updated] (PHOENIX-5333) A tool to upgrade existing tables/indexes to use self-consistent global indexes design

2019-06-21 Thread Swaroopa Kadam (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam updated PHOENIX-5333: Attachment: (was: PHOENIX-5333.master.v1.patch) > A tool to upgrade existing tables/i

[jira] [Updated] (PHOENIX-5309) Skip adding log4j and slf4j to phoenix-hive jar to avoid logging in hive-server2.err file than hiveserver2.log

2019-06-21 Thread Rajeshbabu Chintaguntla (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-5309: - Attachment: PHOENIX-5309_v2.patch > Skip adding log4j and slf4j to phoe

[VOTE] PHOENIX-4863: Setup Travis-CI & CodeCoverage

2019-06-21 Thread Priyank Porwal
[Converting this thread to a community vote] I'd like to start Travis-CI and CodeCov integration after getting some success with both on a fork in my personal account. Checkout - https://github.com/priyankporwal/phoenix/pull/3 Things to note: 1. TravisCI kicked-off as soon as the PR is created an