Re: new 4.8.0 RC?

What I do to allow commit even while running the tests is to create a tag in tag and then run jenkins against that tag instead of a branch. -- Lars From: Ankit Singhal To: dev@phoenix.apache.org Sent: Wednesday, August 3, 2016 1:35 AM Subject: Re: new 4.8.0

Re: JDBC Connection time

@william Thanks for your advice. This is my source code to understand your reply. import java.sql.*; import java.util.*; public class phoenixTest { public static void main(String args[]) throws Exception { Connection conn; //Properties prop = new Properties();

[jira] [Commented] (PHOENIX-3135) Support loading csv data using apache phoenix flume plugin

[ https://issues.apache.org/jira/browse/PHOENIX-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406851#comment-15406851 ] Josh Mahonin commented on PHOENIX-3135: --- Similar to PHOENIX-2084, Phoenix already brings in a

[jira] [Commented] (PHOENIX-2084) Support loading json data using apache phoenix flume plugin

[ https://issues.apache.org/jira/browse/PHOENIX-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406848#comment-15406848 ] Josh Mahonin commented on PHOENIX-2084: --- This looks good to me overall. However, I notice you're

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406847#comment-15406847 ] Enis Soztutar commented on PHOENIX-3111: Indeed. We have a test suite which is supposed to run

[jira] [Commented] (PHOENIX-2547) Spark Data Source API: Filter operation doesn't work for column names containing a white space

[ https://issues.apache.org/jira/browse/PHOENIX-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406837#comment-15406837 ] Josh Mahonin commented on PHOENIX-2547: --- Nice work [~kalyanhadoop] Very straight forward, and the

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406664#comment-15406664 ] James Taylor commented on PHOENIX-3111: --- I believe the folks over at Hortonworks have some manual

[jira] [Created] (PHOENIX-3146) Create stress tests for Phoenix

James Taylor created PHOENIX-3146: - Summary: Create stress tests for Phoenix Key: PHOENIX-3146 URL: https://issues.apache.org/jira/browse/PHOENIX-3146 Project: Phoenix Issue Type: Bug

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406591#comment-15406591 ] Lars Hofhansl commented on PHOENIX-3111: So just for the record... This is a pretty dangerous

[GitHub] phoenix pull request #187: Refactor tests

Github user prakul closed the pull request at: https://github.com/apache/phoenix/pull/187 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: post RC follow up tasks

Unless anyone has objections, I'd like to do the above by the EOD. Please let me know. Thanks, James On Wed, Aug 3, 2016 at 10:49 AM, James Taylor wrote: > Thanks for getting the RC up, Ankit. There are a few minor post RC tasks > to do: > - drop the 4.8 branches and

[jira] [Created] (PHOENIX-3145) Deriving IndexIT from BaseHBaseManagedTimeTableReuseIT causes tests to timeout

James Taylor created PHOENIX-3145: - Summary: Deriving IndexIT from BaseHBaseManagedTimeTableReuseIT causes tests to timeout Key: PHOENIX-3145 URL: https://issues.apache.org/jira/browse/PHOENIX-3145

[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY

[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2885: -- Description: Instead of by default doing an extra RPC per query, we should have a default

[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY

[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2885: -- Description: Instead of by default doing an extra RPC per query, we should have a default

[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY

[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2885: -- Description: Instead of by default doing an extra RPC per query, we should have a default

[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY

[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2885: -- Summary: Set default value for UPDATE_CACHE_FREQUENCY (was: Refresh client side cache before

post RC follow up tasks

Thanks for getting the RC up, Ankit. There are a few minor post RC tasks to do: - drop the 4.8 branches and recreate at head of 4.x branches (since that what the release is based off of) - update the poms in 4.x and master branches to be 4.9.0-HBase-1.2-SNAPSHOT I'm happy to help with these. Just

[jira] [Created] (PHOENIX-3144) Invoking org.apache.phoenix.mapreduce.CsvBulkLoadTool from phoenix-4.4.0.2.4.0.0-169-client.jar is not working properly

Radha Krishna G created PHOENIX-3144: Summary: Invoking org.apache.phoenix.mapreduce.CsvBulkLoadTool from phoenix-4.4.0.2.4.0.0-169-client.jar is not working properly Key: PHOENIX-3144 URL:

Re:JDBC Connection time

It will cost that much indeed. If you connect to an HBase cluster with HBase native API, it will cost that much too. But this is only for the 'first' connection in current JVM process. You can modify your test code and check how long it takes for the second or third connection. It will be less

[jira] [Commented] (PHOENIX-3143) Update KEYS file for 4.8 release

[ https://issues.apache.org/jira/browse/PHOENIX-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405714#comment-15405714 ] Hudson commented on PHOENIX-3143: - SUCCESS: Integrated in Phoenix-master #1354 (See

[VOTE] Release of Apache Phoenix 4.8.0 RC1

Hello Everyone, This is a call for a vote on Apache Phoenix 4.8.0 RC1. This is the next minor release of Phoenix 4, compatible with Apache HBase 0.98,1.0, 1.1 & 1.2. The release includes both a source-only release and a convenience binary release for each supported HBase version. This release

[jira] [Commented] (PHOENIX-3114) PhoenixMRJobSubmitter fails to create async secondary indexes after PHOENIX-2966

[ https://issues.apache.org/jira/browse/PHOENIX-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405618#comment-15405618 ] Ravi Kishore Valeti commented on PHOENIX-3114: -- [~jamestaylor] Background on my post. You

[jira] [Resolved] (PHOENIX-3143) Update KEYS file for 4.8 release

[ https://issues.apache.org/jira/browse/PHOENIX-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3143. Resolution: Fixed Fix Version/s: 4.8.0 > Update KEYS file for 4.8 release >

[jira] [Created] (PHOENIX-3143) Update KEYS file for 4.8 release

Ankit Singhal created PHOENIX-3143: -- Summary: Update KEYS file for 4.8 release Key: PHOENIX-3143 URL: https://issues.apache.org/jira/browse/PHOENIX-3143 Project: Phoenix Issue Type: Bug

[jira] [Updated] (PHOENIX-3120) AsyncIndexRebuilderTask fails for transactional tables

[ https://issues.apache.org/jira/browse/PHOENIX-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3120: --- Fix Version/s: (was: 4.8.1) 4.8.0 > AsyncIndexRebuilderTask fails

Re: new 4.8.0 RC?

Yeah. Let's cut RC from 4.x only as there is not much difference except PHOENIX-3138, PHOENIX-3128,PHOENIX-3120. Which I think are fine for 4.8.0 too I'm running some tests for RC so no more commit please. On Wed, Aug 3, 2016 at 5:42 AM, James Taylor wrote: > I only

[jira] [Moved] (PHOENIX-3142) Phoenix issue-Distribution-IBM BigInsights- Hbase(1.1.1)-Phoenix 4.7

[ https://issues.apache.org/jira/browse/PHOENIX-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S moved ATLAS-1084 to PHOENIX-3142: - Workflow: no-reopen-closed, patch-avail (was: patch-available, re-open

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405475#comment-15405475 ] Hudson commented on PHOENIX-3111: - SUCCESS: Integrated in Phoenix-master #1353 (See

[jira] [Commented] (PHOENIX-3141) UnnestArrayIT causes builds to hang

[ https://issues.apache.org/jira/browse/PHOENIX-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405474#comment-15405474 ] Hudson commented on PHOENIX-3141: - SUCCESS: Integrated in Phoenix-master #1353 (See