Re: [ANNOUNCE] New Phoenix PMC member: Vincent Poon

[Mujtaba Chohan]

Congrats Vincent!!!

On Tue, Jun 12, 2018 at 10:15 AM, Karan Mehta 
wrote:

> Awesome Vincent, Congrats!!
>
> On Mon, Jun 11, 2018 at 7:20 PM James Taylor 
> wrote:
>
> > On behalf of the Apache Phoenix PMC, I'm please to announce that Vincent
> > Poon has accepted our invitation to join the PMC. He's been focused on
> > improving the stability and performance of secondary indexing over the
> last
> > several releases.
> >
> > Please congratulate Vincent on the fantastic job he's doing.
> >
> > Thanks,
> > James
> >
>

Re: [VOTE] Release of Apache Phoenix 4.14.0 RC3

[Mujtaba Chohan]

+1.

Verified backward compat. and performance looks fine when compared to last
release (0.98 branch).

On Tue, Jun 5, 2018 at 11:50 AM, Pedro Boado  wrote:

> Sure, I'll add the signature to the release repo (it's already in the dev
> repo) . Thanks for the reminder.
>
> On Tue, 5 Jun 2018, 19:36 Josh Elser,  wrote:
>
> > +1 (binding)
> >
> > The KEYS file *must* be updated before this is released. Pedro's key
> > does not exist at
> > https://dist.apache.org/repos/dist/release/phoenix/KEYS. Pedro, can you
> > add your key to the bottom of that file, please? There are instructions
> > at the top of the file.
> >
> > * can build all from src
> > * xsums are OK, sigs are ok (given the above caveat)
> > * No unexpected binaries in src release
> > * mvn apache-rat:check fails in all CDH branches, but only on a
> .gitignore
> > * the hbase-1.1 branch is still missing the change to checksum
> > generation, so it is "special" (not an issue if we just drop it anyways)
> > but not wrong.
> >
> > On 6/5/18 10:23 AM, James Taylor wrote:
> > > Hello Everyone,
> > >
> > > This is a call for a vote on Apache Phoenix 4.14.0 RC3. This is a patch
> > > release of Phoenix 4.14 and is compatible with Apache HBase 0.98, 1.1,
> > 1.2,
> > > 1.3, 1.4 and CDH 5.11, 5.12, 5.13, and 5.14. The release includes both
> a
> > > source-only release and a convenience binary release for each supported
> > > HBase version. The prior RC was sunk due to PHOENIX-4759 which is now
> > fixed.
> > >
> > > This release has feature parity with supported HBase versions and
> > includes
> > > the following improvements:
> > > - Over 90 bug fixes
> > > - Support for HBase 1.4
> > > - Support for more CDH releases
> > > - Support for GRANT/REVOKE [1][2]
> > > - Avoid server retries for mutable indexes [3]
> > > - Pure client side transactional index maintenance [4]
> > > - Prune local index regions scanned during query execution [5][6]
> > > - Support NOT NULL constraint for any column for immutable table [7]
> > >
> > > The source tarball, including signatures, digests, etc can be found at:
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-0.98-rc3/src/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-1.1-rc3/src/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-1.2-rc3/src/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-1.3-rc3/src/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-1.4-rc3/src/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.11.2-rc3/src/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.12.2-rc3/src/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.13.2-rc3/src/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.14.2-rc3/src/
> > >
> > > The binary artifacts can be found at:
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-0.98-rc3/bin/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-1.1-rc3/bin/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-1.2-rc3/bin/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-1.3-rc3/bin/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-1.4-rc3/bin/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.11.2-rc3/bin/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.12.2-rc3/bin/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.13.2-rc3/bin/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.14.2-rc3/bin/
> > >
> > > The binary parcels for CDH can be found at:
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.11.2-rc3/parcels/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.12.2-rc3/parcels/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.13.2-rc3/parcels/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.14.2-rc3/parcels/
> > >
> > > For a complete list of changes, see:
> > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12315120=12342145
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/mujtaba.asc (hbase versions)
> > > https://people.apache.org/keys/committer/pboado.asc (cdh versions)
> > > https://dist.apache.org/repos/dist/release/phoenix/KEYS
> > >
> > > The hash and tag to be voted upon:
> > >
> > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=
> 

Re: [VOTE] Release of Apache Phoenix 4.14.0 RC1

[Mujtaba Chohan]

+1.

Verified backward compatibility and perf. to be on par with previous
release (0.98 branch).

On Wed, May 30, 2018 at 3:39 PM, Pedro Boado  wrote:

> +1
>
> Tested (installed from parcels) in CDH 5.11.2 updating from Phoenix 4.13.2
> to 4.14.0 (basic table operation seems fine, no issues found) and also a
> clean install in clusters running CDH 5.12, 5.13 and 5.14 ( also with basic
> table operations ). Built from sources with all IT passing in all CDH
> branches.
>
> On Wed, 30 May 2018, 22:56 Josh Elser,  wrote:
>
> > +1 (binding)
> >
> > Disclaimer: I only looked at the source releases. Too many other
> > convenience binaries to pull it all down and validate individually.
> >
> > * hbase-1.1 had a slightly different xsum (.sha instead of .sha256 and
> > .sha512) -- not sure if this was just caused by a human
> > * xsums/sigs all fine
> > * Validated no unexpected files, rat:check passed, could build from
> source
> >
> > On 5/27/18 5:55 PM, James Taylor wrote:
> > > Hello Everyone,
> > >
> > > This is a call for a vote on Apache Phoenix 4.14.0 RC1. This is a patch
> > > release of Phoenix 4.14 and is compatible with Apache HBase 0.98, 1.1,
> > 1.2,
> > > 1.3, 1.4 and CDH 5.11, 5.12, 5.13, and 5.14. The release includes both
> a
> > > source-only release and a convenience binary release for each supported
> > > HBase version. The prior RC was sunk due to PHOENIX-4685 which is now
> > fixed.
> > >
> > > This release has feature parity with supported HBase versions and
> > includes
> > > the following improvements:
> > > - Over 90 bug fixes
> > > - Support for HBase 1.4
> > > - Support for more CDH releases
> > > - Support for GRANT/REVOKE [1][2]
> > > - Avoid server retries for mutable indexes [3]
> > > - Pure client side transactional index maintenance [4]
> > > - Prune local index regions scanned during query execution [5][6]
> > > - Support NOT NULL constraint for any column for immutable table [7]
> > >
> > > The source tarball, including signatures, digests, etc can be found at:
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-0.98-rc1/src/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-1.1-rc1/src/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-1.2-rc1/src/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-1.3-rc1/src/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-1.4-rc1/src/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.11.2-rc1/src/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.12.2-rc1/src/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.13.2-rc1/src/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.14.2-rc1/src/
> > >
> > > The binary artifacts can be found at:
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-0.98-rc1/bin/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-1.1-rc1/bin/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-1.2-rc1/bin/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-1.3-rc1/bin/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-HBase-1.4-rc1/bin/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.11.2-rc1/bin/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.12.2-rc1/bin/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.13.2-rc1/bin/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.14.2-rc1/bin/
> > >
> > > The binary parcels for CDH can be found at:
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.11.2-rc1/parcels/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.12.2-rc1/parcels/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.13.2-rc1/parcels/
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> phoenix-4.14.0-cdh5.14.2-rc1/parcels/
> > >
> > > For a complete list of changes, see:
> > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12315120=12342145
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/mujtaba.asc (hbase versions)
> > > https://people.apache.org/keys/committer/pboado.asc (cdh versions)
> > > https://dist.apache.org/repos/dist/release/phoenix/KEYS
> > >
> > > The hash and tag to be voted upon:
> > >
> > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=
> 5b3fd404184cc6291bb2d3773e5e0b40c193cf01
> > >
> > 

[jira] [Commented] (PHOENIX-4742) DistinctPrefixFilter potentially seeks to lesser key when descending or null value

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481356#comment-16481356
 ] 

Mujtaba Chohan commented on PHOENIX-4742:
-

+1. LGTM. 

> DistinctPrefixFilter potentially seeks to lesser key when descending or null 
> value
> --
>
> Key: PHOENIX-4742
> URL: https://issues.apache.org/jira/browse/PHOENIX-4742
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Fix For: 4.14.0, 5.0.0
>
> Attachments: PHOENIX-4742_v1.patch
>
>
> DistinctPrefixFilter seeks to a smaller key than the current key (which 
> causes an infinite loop in HBase 1.4 and seeks to every row in other HBase 
> versions). This happens when:
>  # Last column of distinct is descending. We currently always add a 0x01 
> byte, but since the separator byte if 0xFF when descending, the seek key is 
> too small.
>  # Last column value is null. In this case, instead of adding a 0x01 byte, we 
> need to increment in-place the null value of the last distinct column. 
> This was discovered due to 
> OrderByIT.testOrderByReverseOptimizationWithNUllsLastBug3491 hanging in 
> master.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (PHOENIX-4706) phoenix-core jar bundles dependencies unnecessarily

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481073#comment-16481073
 ] 

Mujtaba Chohan commented on PHOENIX-4706:
-

[~elserj] +1. It only bundled antlr runtime which should be safe to remove. BTW 
sorry for the delay in response.

> phoenix-core jar bundles dependencies unnecessarily
> ---
>
> Key: PHOENIX-4706
> URL: https://issues.apache.org/jira/browse/PHOENIX-4706
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Major
> Fix For: 4.15.0
>
> Attachments: PHOENIX-4706.001.patch
>
>
> Got a report from some users about extra dependencies being included inside 
> the phoenix-core jar. I was a little confused about this, but, sure enough, 
> it's happening.
> Seems like this was done a very long time ago, but I'm not sure that it's 
> really something we want to do since there is a dedicated phoenix-client jar 
> now..



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (PHOENIX-4718) Decrease overhead of tracking aggregate heap size

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459840#comment-16459840
 ] 

Mujtaba Chohan commented on PHOENIX-4718:
-

[~jamestaylor] verified that performance is inline with previous releases with 
the patch applied.

> Decrease overhead of tracking aggregate heap size
> -
>
> Key: PHOENIX-4718
> URL: https://issues.apache.org/jira/browse/PHOENIX-4718
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Fix For: 4.14.0, 5.0.0
>
> Attachments: PHOENIX-4718-4.x-HBase-0.98.patch, PHOENIX-4718.patch, 
> PHOENIX-4718_v2.patch, PHOENIX-4718_v3.patch
>
>
> Since PHOENIX-4148, we track the heap size while aggregation is occurring. 
> This decreased performance of aggregation by ~20%. We really only need to 
> track this for the DistinctValueWithCountServerAggregator (used by DISTINCT 
> COUNT, DISTINCT, PERCENTILE functions, and STDDEV functions). By 
> conditionally tracking, we should be able to bring perf back to what it was 
> before.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (PHOENIX-4718) Decrease overhead of tracking aggregate heap size

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459261#comment-16459261
 ] 

Mujtaba Chohan commented on PHOENIX-4718:
-

I'll check that [~jamestaylor]

> Decrease overhead of tracking aggregate heap size
> -
>
> Key: PHOENIX-4718
> URL: https://issues.apache.org/jira/browse/PHOENIX-4718
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Attachments: PHOENIX-4718-4.x-HBase-0.98.patch, PHOENIX-4718.patch, 
> PHOENIX-4718_v2.patch
>
>
> Since PHOENIX-4148, we track the heap size while aggregation is occurring. 
> This decreased performance of aggregation by ~20%. We really only need to 
> track this for the DistinctValueWithCountServerAggregator (used by DISTINCT 
> COUNT, DISTINCT, PERCENTILE functions, and STDDEV functions). By 
> conditionally tracking, we should be able to bring perf back to what it was 
> before.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (PHOENIX-4705) Use XMLInputFactory.newInstance() instead of XMLInputFactory.newFactory()

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16455507#comment-16455507
 ] 

Mujtaba Chohan commented on PHOENIX-4705:
-

Thanks [~jamestaylor]. +1.

> Use XMLInputFactory.newInstance() instead of XMLInputFactory.newFactory()
> -
>
> Key: PHOENIX-4705
> URL: https://issues.apache.org/jira/browse/PHOENIX-4705
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Fix For: 4.14.0, 5.0.0
>
> Attachments: PHOENIX-4705.patch
>
>
> Use XMLInputFactory.newInstance() instead of XMLInputFactory.newFactory() in 
> Pherf as the latter doesn't compile (at least for me).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (PHOENIX-4705) Use XMLInputFactory.newInstance() instead of XMLInputFactory.newFactory()

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16454735#comment-16454735
 ] 

Mujtaba Chohan commented on PHOENIX-4705:
-

https://bugs.openjdk.java.net/browse/JDK-8183519

> Use XMLInputFactory.newInstance() instead of XMLInputFactory.newFactory()
> -
>
> Key: PHOENIX-4705
> URL: https://issues.apache.org/jira/browse/PHOENIX-4705
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
>
> Use XMLInputFactory.newInstance() instead of XMLInputFactory.newFactory() in 
> Pherf as the latter doesn't compile (at least for me).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (PHOENIX-4699) Stop scan after finding first child of table during drop

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444892#comment-16444892
 ] 

Mujtaba Chohan commented on PHOENIX-4699:
-

+1

> Stop scan after finding first child of table during drop
> 
>
> Key: PHOENIX-4699
> URL: https://issues.apache.org/jira/browse/PHOENIX-4699
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Priority: Major
> Fix For: 4.14.0, 5.0.0
>
> Attachments: PHOENIX-4699.patch
>
>
> Rather than scan all children when dropping a table or view, we should stop 
> at the first one (unless we've issued a drop cascade).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (PHOENIX-4414) Exception while using database metadata commands on tenant specific connection

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370789#comment-16370789
 ] 

Mujtaba Chohan commented on PHOENIX-4414:
-

[~rajeshbabu] done.

> Exception while using database metadata commands on tenant specific connection
> --
>
> Key: PHOENIX-4414
> URL: https://issues.apache.org/jira/browse/PHOENIX-4414
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.14.0
>        Reporter: Mujtaba Chohan
>    Assignee: Mujtaba Chohan
>Priority: Minor
> Attachments: PHOENIX-4414.patch, PHOENIX-4414_v2.patch
>
>
> This is when using tenant specific connection from Sqlline.
> {noformat}
> Error: ERROR 602 (42P00): Syntax error. Missing "LPAREN" at line 2, column 
> 746. (state=42P00,code=602)
> org.apache.phoenix.exception.PhoenixParserException: ERROR 602 (42P00): 
> Syntax error. Missing "LPAREN" at line 2, column 746.
>   at 
> org.apache.phoenix.exception.PhoenixParserException.newException(PhoenixParserException.java:33)
>   at org.apache.phoenix.parse.SQLParser.parseStatement(SQLParser.java:111)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement$PhoenixStatementParser.parseStatement(PhoenixStatement.java:1529)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement.parseStatement(PhoenixStatement.java:1612)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:1653)
>   at 
> org.apache.phoenix.jdbc.PhoenixDatabaseMetaData.getColumns(PhoenixDatabaseMetaData.java:557)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (PHOENIX-4549) Pherf - Column override and sequenced index creation support

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan resolved PHOENIX-4549.
-
Resolution: Fixed

> Pherf - Column override and sequenced index creation support
> 
>
> Key: PHOENIX-4549
> URL: https://issues.apache.org/jira/browse/PHOENIX-4549
> Project: Phoenix
>  Issue Type: Improvement
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
>Priority: Major
> Fix For: 4.14.0
>
> Attachments: PHOENIX-4549.patch
>
>
> Support for column level override for upserting view specific data along with 
> sequenced index creation either before or after data is loaded. Patch also 
> contains additional datatype support (TIMESTAMP, VARCHAR_ARRAY. VARBINARY AND 
> UNSIGNED_LONG)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (PHOENIX-4549) Pherf - Column override and sequenced index creation support

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4549:

Fix Version/s: 4.14.0

> Pherf - Column override and sequenced index creation support
> 
>
> Key: PHOENIX-4549
> URL: https://issues.apache.org/jira/browse/PHOENIX-4549
> Project: Phoenix
>  Issue Type: Improvement
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
>Priority: Major
> Fix For: 4.14.0
>
> Attachments: PHOENIX-4549.patch
>
>
> Support for column level override for upserting view specific data along with 
> sequenced index creation either before or after data is loaded. Patch also 
> contains additional datatype support (TIMESTAMP, VARCHAR_ARRAY. VARBINARY AND 
> UNSIGNED_LONG)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (PHOENIX-4575) Phoenix metadata KEEP_DELETED_CELLS and VERSIONS should be property driven

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16356121#comment-16356121
 ] 

Mujtaba Chohan commented on PHOENIX-4575:
-

[~jamestaylor]

> Phoenix metadata KEEP_DELETED_CELLS and VERSIONS should be property driven
> --
>
> Key: PHOENIX-4575
> URL: https://issues.apache.org/jira/browse/PHOENIX-4575
> Project: Phoenix
>  Issue Type: New Feature
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
>Priority: Major
> Attachments: PHOENIX-4575.patch, PHOENIX-4575_v2.patch
>
>
> This is to cater for circumstances where we need to alter state of 
> KEEP_DELETED_CELLS/VERSION on Phoenix meta tables.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (PHOENIX-4579) Add a config to conditionally create Phoenix meta tables on first client connection

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16356120#comment-16356120
 ] 

Mujtaba Chohan commented on PHOENIX-4579:
-

[~jamestaylor]

> Add a config to conditionally create Phoenix meta tables on first client 
> connection
> ---
>
> Key: PHOENIX-4579
> URL: https://issues.apache.org/jira/browse/PHOENIX-4579
> Project: Phoenix
>  Issue Type: New Feature
>        Reporter: Mujtaba Chohan
>    Assignee: Mujtaba Chohan
>Priority: Major
> Attachments: PHOENIX-4579.patch
>
>
> Currently we create/modify Phoenix meta tables on first client connection. 
> Adding a property to make it configurable (with default true as it is 
> currently implemented).
> With this property set to false, it will avoid lockstep upgrade requirement 
> for all clients when changing meta properties using PHOENIX-4575 as this 
> property can be flipped back on once all the clients are upgraded.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (PHOENIX-4579) Add a config to conditionally create Phoenix meta tables on first client connection

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16352784#comment-16352784
 ] 

Mujtaba Chohan commented on PHOENIX-4579:
-

Added {{phoenix.system.upgrade.first.connection}} which is true by default 
(existing behavior) but can be turned off in config.

> Add a config to conditionally create Phoenix meta tables on first client 
> connection
> ---
>
> Key: PHOENIX-4579
> URL: https://issues.apache.org/jira/browse/PHOENIX-4579
> Project: Phoenix
>  Issue Type: New Feature
>        Reporter: Mujtaba Chohan
>Priority: Major
> Attachments: PHOENIX-4579.patch
>
>
> Currently we create/modify Phoenix meta tables on first client connection. 
> Adding a property to make it configurable (with default true as it is 
> currently implemented).
> With this property set to false, it will avoid lockstep upgrade requirement 
> for all clients when changing meta properties using PHOENIX-4575 as this 
> property can be flipped back on once all the clients are upgraded.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (PHOENIX-4579) Add a config to conditionally create Phoenix meta tables on first client connection

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan reassigned PHOENIX-4579:
---

Assignee: Mujtaba Chohan

> Add a config to conditionally create Phoenix meta tables on first client 
> connection
> ---
>
> Key: PHOENIX-4579
> URL: https://issues.apache.org/jira/browse/PHOENIX-4579
> Project: Phoenix
>  Issue Type: New Feature
>        Reporter: Mujtaba Chohan
>    Assignee: Mujtaba Chohan
>Priority: Major
> Attachments: PHOENIX-4579.patch
>
>
> Currently we create/modify Phoenix meta tables on first client connection. 
> Adding a property to make it configurable (with default true as it is 
> currently implemented).
> With this property set to false, it will avoid lockstep upgrade requirement 
> for all clients when changing meta properties using PHOENIX-4575 as this 
> property can be flipped back on once all the clients are upgraded.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (PHOENIX-4579) Add a config to conditionally create Phoenix meta tables on first client connection

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4579:

Attachment: PHOENIX-4579.patch

> Add a config to conditionally create Phoenix meta tables on first client 
> connection
> ---
>
> Key: PHOENIX-4579
> URL: https://issues.apache.org/jira/browse/PHOENIX-4579
> Project: Phoenix
>  Issue Type: New Feature
>        Reporter: Mujtaba Chohan
>Priority: Major
> Attachments: PHOENIX-4579.patch
>
>
> Currently we create/modify Phoenix meta tables on first client connection. 
> Adding a property to make it configurable (with default true as it is 
> currently implemented).
> With this property set to false, it will avoid lockstep upgrade requirement 
> for all clients when changing meta properties using PHOENIX-4575 as this 
> property can be flipped back on once all the clients are upgraded.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (PHOENIX-4579) Add a config to conditionally create Phoenix meta tables on first client connection

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4579:
---

 Summary: Add a config to conditionally create Phoenix meta tables 
on first client connection
 Key: PHOENIX-4579
 URL: https://issues.apache.org/jira/browse/PHOENIX-4579
 Project: Phoenix
  Issue Type: New Feature
Reporter: Mujtaba Chohan


Currently we create/modify Phoenix meta tables on first client connection. 
Adding a property to make it configurable (with default true as it is currently 
implemented).

With this property set to false, it will avoid lockstep upgrade requirement for 
all clients when changing meta properties using PHOENIX-4575 as this property 
can be flipped back on once all the clients are upgraded.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (PHOENIX-4575) Phoenix metadata KEEP_DELETED_CELLS and VERSIONS should be property driven

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349204#comment-16349204
 ] 

Mujtaba Chohan commented on PHOENIX-4575:
-

[~jamestaylor] FYI attached v2 patch.

> Phoenix metadata KEEP_DELETED_CELLS and VERSIONS should be property driven
> --
>
> Key: PHOENIX-4575
> URL: https://issues.apache.org/jira/browse/PHOENIX-4575
> Project: Phoenix
>  Issue Type: New Feature
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
>Priority: Major
> Attachments: PHOENIX-4575.patch, PHOENIX-4575_v2.patch
>
>
> This is to cater for circumstances where we need to alter state of 
> KEEP_DELETED_CELLS/VERSION on Phoenix meta tables.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (PHOENIX-4575) Phoenix metadata KEEP_DELETED_CELLS and VERSIONS should be property driven

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4575:

Attachment: PHOENIX-4575_v2.patch

> Phoenix metadata KEEP_DELETED_CELLS and VERSIONS should be property driven
> --
>
> Key: PHOENIX-4575
> URL: https://issues.apache.org/jira/browse/PHOENIX-4575
> Project: Phoenix
>  Issue Type: New Feature
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
>Priority: Major
> Attachments: PHOENIX-4575.patch, PHOENIX-4575_v2.patch
>
>
> This is to cater for circumstances where we need to alter state of 
> KEEP_DELETED_CELLS/VERSION on Phoenix meta tables.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (PHOENIX-4575) Phoenix metadata KEEP_DELETED_CELLS and VERSIONS should be property driven

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348034#comment-16348034
 ] 

Mujtaba Chohan commented on PHOENIX-4575:
-

Thanks for the review [~jamestaylor]. I’ll work on the changes. 

> Phoenix metadata KEEP_DELETED_CELLS and VERSIONS should be property driven
> --
>
> Key: PHOENIX-4575
> URL: https://issues.apache.org/jira/browse/PHOENIX-4575
> Project: Phoenix
>  Issue Type: New Feature
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
>Priority: Major
> Attachments: PHOENIX-4575.patch
>
>
> This is to cater for circumstances where we need to alter state of 
> KEEP_DELETED_CELLS/VERSION on Phoenix meta tables.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (PHOENIX-4575) Phoenix metadata KEEP_DELETED_CELLS and VERSIONS should be property driven

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347730#comment-16347730
 ] 

Mujtaba Chohan commented on PHOENIX-4575:
-

Attached patch adds 2 new properties that can be set in hbase-site.xml: 
 # phoenix.metadata.keep.deleted.cells
 # phoenix.metadata.max.versions

 

> Phoenix metadata KEEP_DELETED_CELLS and VERSIONS should be property driven
> --
>
> Key: PHOENIX-4575
> URL: https://issues.apache.org/jira/browse/PHOENIX-4575
> Project: Phoenix
>  Issue Type: New Feature
>    Reporter: Mujtaba Chohan
>Priority: Major
> Attachments: PHOENIX-4575.patch
>
>
> This is to cater for circumstances where we need to alter state of 
> KEEP_DELETED_CELLS/VERSION on Phoenix meta tables.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (PHOENIX-4575) Phoenix metadata KEEP_DELETED_CELLS and VERSIONS should be property driven

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan reassigned PHOENIX-4575:
---

Assignee: Mujtaba Chohan

> Phoenix metadata KEEP_DELETED_CELLS and VERSIONS should be property driven
> --
>
> Key: PHOENIX-4575
> URL: https://issues.apache.org/jira/browse/PHOENIX-4575
> Project: Phoenix
>  Issue Type: New Feature
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
>Priority: Major
> Attachments: PHOENIX-4575.patch
>
>
> This is to cater for circumstances where we need to alter state of 
> KEEP_DELETED_CELLS/VERSION on Phoenix meta tables.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (PHOENIX-4575) Phoenix metadata KEEP_DELETED_CELLS and VERSIONS should be property driven

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4575:
---

 Summary: Phoenix metadata KEEP_DELETED_CELLS and VERSIONS should 
be property driven
 Key: PHOENIX-4575
 URL: https://issues.apache.org/jira/browse/PHOENIX-4575
 Project: Phoenix
  Issue Type: New Feature
Reporter: Mujtaba Chohan
 Attachments: PHOENIX-4575.patch

This is to cater for circumstances where we need to alter state of 
KEEP_DELETED_CELLS/VERSION on Phoenix meta tables.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (PHOENIX-4575) Phoenix metadata KEEP_DELETED_CELLS and VERSIONS should be property driven

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4575:

Attachment: PHOENIX-4575.patch

> Phoenix metadata KEEP_DELETED_CELLS and VERSIONS should be property driven
> --
>
> Key: PHOENIX-4575
> URL: https://issues.apache.org/jira/browse/PHOENIX-4575
> Project: Phoenix
>  Issue Type: New Feature
>    Reporter: Mujtaba Chohan
>Priority: Major
> Attachments: PHOENIX-4575.patch
>
>
> This is to cater for circumstances where we need to alter state of 
> KEEP_DELETED_CELLS/VERSION on Phoenix meta tables.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (PHOENIX-4414) Exception while using database metadata commands on tenant specific connection

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan resolved PHOENIX-4414.
-
Resolution: Fixed

> Exception while using database metadata commands on tenant specific connection
> --
>
> Key: PHOENIX-4414
> URL: https://issues.apache.org/jira/browse/PHOENIX-4414
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.14.0
>        Reporter: Mujtaba Chohan
>    Assignee: Mujtaba Chohan
>Priority: Minor
> Attachments: PHOENIX-4414.patch, PHOENIX-4414_v2.patch
>
>
> This is when using tenant specific connection from Sqlline.
> {noformat}
> Error: ERROR 602 (42P00): Syntax error. Missing "LPAREN" at line 2, column 
> 746. (state=42P00,code=602)
> org.apache.phoenix.exception.PhoenixParserException: ERROR 602 (42P00): 
> Syntax error. Missing "LPAREN" at line 2, column 746.
>   at 
> org.apache.phoenix.exception.PhoenixParserException.newException(PhoenixParserException.java:33)
>   at org.apache.phoenix.parse.SQLParser.parseStatement(SQLParser.java:111)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement$PhoenixStatementParser.parseStatement(PhoenixStatement.java:1529)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement.parseStatement(PhoenixStatement.java:1612)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:1653)
>   at 
> org.apache.phoenix.jdbc.PhoenixDatabaseMetaData.getColumns(PhoenixDatabaseMetaData.java:557)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (PHOENIX-4549) Pherf - Column override and sequenced index creation support

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4549:
---

 Summary: Pherf - Column override and sequenced index creation 
support
 Key: PHOENIX-4549
 URL: https://issues.apache.org/jira/browse/PHOENIX-4549
 Project: Phoenix
  Issue Type: Improvement
Reporter: Mujtaba Chohan
Assignee: Mujtaba Chohan
 Attachments: PHOENIX-4549.patch

Support for column level override for upserting view specific data along with 
sequenced index creation either before or after data is loaded. Patch also 
contains additional datatype support (TIMESTAMP, VARCHAR_ARRAY. VARBINARY AND 
UNSIGNED_LONG)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (PHOENIX-4549) Pherf - Column override and sequenced index creation support

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4549:

Attachment: PHOENIX-4549.patch

> Pherf - Column override and sequenced index creation support
> 
>
> Key: PHOENIX-4549
> URL: https://issues.apache.org/jira/browse/PHOENIX-4549
> Project: Phoenix
>  Issue Type: Improvement
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
>Priority: Major
> Attachments: PHOENIX-4549.patch
>
>
> Support for column level override for upserting view specific data along with 
> sequenced index creation either before or after data is loaded. Patch also 
> contains additional datatype support (TIMESTAMP, VARCHAR_ARRAY. VARBINARY AND 
> UNSIGNED_LONG)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release of Apache Phoenix 4.13.2 for CDH 5.11.2 RC0

[Mujtaba Chohan]

+1. Ran tests and verified signatures.

On Tue, Jan 16, 2018 at 10:27 AM, Samarth Jain  wrote:

> +1. Ran unit tests successfully. Executed some manual tests around
> secondary indexes and stats collection - looks fine.
>
> On Sat, Jan 13, 2018 at 3:30 AM, Pedro Boado 
> wrote:
>
> > Hello Everyone,
> >
> > This is a call for a vote on Apache Phoenix 4.13.2 for CDH 5.11.2 RC0.
> This
> > is
> > a first release of Phoenix 4.13.x compatible with Cloudera CDH. The
> release
> > includes a source-only release, a convenience binary release and, as a
> > novelty, a
> > parcel-based binary release ready to be installed from Cloudera Manager
> > (CM).
> >
> > This release has feature parity with supported HBase versions and
> includes
> > the following improvements:
> > - Support for Apache Phoenix on CDH 5.11.2 ( based on HBase 1.2 branch )
> .
> > - More than 10+ fixes over release 4.13.1-HBase-1.2
> >
> > The work is inspired on the approach taken ( and now discontinued ) by
> > https://github.com/cloudera-labs/phoenix a while ago. Please take this
> > first RC for a spin!
> >
> > The source tarball, including signatures, digests, etc can be found at:
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > phoenix-4.13.2-cdh5.11.2-rc0/src/
> >
> > The binary artifacts can be found at:
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > phoenix-4.13.2-cdh5.11.2-rc0/bin/
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-
> > phoenix-4.13.2-cdh5.11.2-rc0/parcels/  ( this
> > directory can be configured in CM as parcel repository for direct
> > installation )
> >
> > For a complete list of changes, see:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > version=12342253=Text=12315120
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/mujtaba.asc
> > https://dist.apache.org/repos/dist/release/phoenix/KEYS
> >
> > The hash and tag to be voted upon:
> > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=
> > 60b76d2dc0a039777cc380cf5a8a927a02afff6d
> > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
> > h=refs/tags/v4.13.2-cdh5.11.2-rc0
> >
> > Vote will be open for at least 72 hours. Please vote:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> > Thanks,
> > The Apache Phoenix Team
> >
>

[jira] [Updated] (PHOENIX-4414) Exception while using database metadata commands on tenant specific connection

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4414:

Attachment: PHOENIX-4414_v2.patch

Added a unit test as well.

> Exception while using database metadata commands on tenant specific connection
> --
>
> Key: PHOENIX-4414
> URL: https://issues.apache.org/jira/browse/PHOENIX-4414
> Project: Phoenix
>  Issue Type: Bug
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
>Priority: Minor
> Attachments: PHOENIX-4414.patch, PHOENIX-4414_v2.patch
>
>
> This is when using tenant specific connection from Sqlline.
> {noformat}
> Error: ERROR 602 (42P00): Syntax error. Missing "LPAREN" at line 2, column 
> 746. (state=42P00,code=602)
> org.apache.phoenix.exception.PhoenixParserException: ERROR 602 (42P00): 
> Syntax error. Missing "LPAREN" at line 2, column 746.
>   at 
> org.apache.phoenix.exception.PhoenixParserException.newException(PhoenixParserException.java:33)
>   at org.apache.phoenix.parse.SQLParser.parseStatement(SQLParser.java:111)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement$PhoenixStatementParser.parseStatement(PhoenixStatement.java:1529)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement.parseStatement(PhoenixStatement.java:1612)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:1653)
>   at 
> org.apache.phoenix.jdbc.PhoenixDatabaseMetaData.getColumns(PhoenixDatabaseMetaData.java:557)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (PHOENIX-4476) Range scan used for point lookups if filter is not in order of primary keys

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16297643#comment-16297643
 ] 

Mujtaba Chohan commented on PHOENIX-4476:
-

FYI [~tdsilva], [~sukumaddineni]

> Range scan used for point lookups if filter is not in order of primary keys
> ---
>
> Key: PHOENIX-4476
> URL: https://issues.apache.org/jira/browse/PHOENIX-4476
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.13.1
>        Reporter: Mujtaba Chohan
>
> {noformat}
> DROP TABLE TEST;
> CREATE TABLE IF NOT EXISTS TEST (
> PK1 CHAR(1) NOT NULL,
> PK2 VARCHAR NOT NULL,
> PK3 VARCHAR NOT NULL,
> PK4 UNSIGNED_LONG NOT NULL,
> PK5 VARCHAR NOT NULL,
> V1 VARCHAR,
> V2 VARCHAR,
> V3 UNSIGNED_LONG
> CONSTRAINT state_pk PRIMARY KEY (
>   PK1,
>   PK2,
>   PK3,
>   PK4,
>   PK5
> )
> );
> // Incorrect explain plan with un-ordered PKs
> EXPLAIN SELECT V1 FROM TEST WHERE (PK1, PK5, PK2, PK3, PK4) IN (('A', 'E', 
> 'N', 'T', 3), ('A', 'Y', 'G', 'T', 4)); 
> +--+--+--+-+
> |   PLAN   |  EST_BYTES_READ  
> |  EST_ROWS_READ   | |
> +--+--+--+-+
> | CLIENT 1-CHUNK PARALLEL 1-WAY ROUND ROBIN RANGE SCAN OVER TEST ['A'] | null 
> | null   |
> | SERVER FILTER BY (PK1, PK5, PK2, PK3, PK4) IN 
> ([65,69,0,78,0,84,0,0,0,0,0,0,0,0,3],[65,89,0,71,0,84,0,0,0,0,0,0,0,0,4]) | 
> null   |
> +--+--+--+-+
> // Correct explain plan with PKs in order
> EXPLAIN SELECT V1 FROM TEST WHERE (PK1,PK2,PK3,PK4,PK5) IN (('A', 'E', 'N',3, 
> 'T'),('A', 'Y', 'G', 4, 'T')); 
> +--+--+--+-+
> |   PLAN   |  EST_BYTES_READ  
> |  EST_ROWS_READ   | |
> +--+--+--+-+
> | CLIENT 1-CHUNK 2 ROWS 712 BYTES PARALLEL 1-WAY ROUND ROBIN POINT LOOKUP ON 
> 2 KEYS OVER TEST | 712  | |
> +--+--+--+-+
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PHOENIX-4476) Range scan used for point lookups if filter is not in order of primary keys

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4476:
---

 Summary: Range scan used for point lookups if filter is not in 
order of primary keys
 Key: PHOENIX-4476
 URL: https://issues.apache.org/jira/browse/PHOENIX-4476
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.13.1
Reporter: Mujtaba Chohan


{noformat}
DROP TABLE TEST;

CREATE TABLE IF NOT EXISTS TEST (
PK1 CHAR(1) NOT NULL,
PK2 VARCHAR NOT NULL,
PK3 VARCHAR NOT NULL,
PK4 UNSIGNED_LONG NOT NULL,
PK5 VARCHAR NOT NULL,
V1 VARCHAR,
V2 VARCHAR,
V3 UNSIGNED_LONG
CONSTRAINT state_pk PRIMARY KEY (
  PK1,
  PK2,
  PK3,
  PK4,
  PK5
)
);

// Incorrect explain plan with un-ordered PKs
EXPLAIN SELECT V1 FROM TEST WHERE (PK1, PK5, PK2, PK3, PK4) IN (('A', 'E', 'N', 
'T', 3), ('A', 'Y', 'G', 'T', 4)); 

+--+--+--+-+
|   PLAN   |  EST_BYTES_READ
  |  EST_ROWS_READ   | |
+--+--+--+-+
| CLIENT 1-CHUNK PARALLEL 1-WAY ROUND ROBIN RANGE SCAN OVER TEST ['A'] | null   
  | null   |
| SERVER FILTER BY (PK1, PK5, PK2, PK3, PK4) IN 
([65,69,0,78,0,84,0,0,0,0,0,0,0,0,3],[65,89,0,71,0,84,0,0,0,0,0,0,0,0,4]) | 
null   |
+--+--+--+-+

// Correct explain plan with PKs in order
EXPLAIN SELECT V1 FROM TEST WHERE (PK1,PK2,PK3,PK4,PK5) IN (('A', 'E', 'N',3, 
'T'),('A', 'Y', 'G', 4, 'T')); 

+--+--+--+-+
|   PLAN   |  EST_BYTES_READ
  |  EST_ROWS_READ   | |
+--+--+--+-+
| CLIENT 1-CHUNK 2 ROWS 712 BYTES PARALLEL 1-WAY ROUND ROBIN POINT LOOKUP ON 2 
KEYS OVER TEST | 712  | |
+--+--+--+-+

{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (PHOENIX-4397) Incorrect query results when with stats are disabled on a salted table

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284452#comment-16284452
 ] 

Mujtaba Chohan commented on PHOENIX-4397:
-

+1. Verified using additional Salesforce internal tests.

> Incorrect query results when with stats are disabled on a salted table
> --
>
> Key: PHOENIX-4397
> URL: https://issues.apache.org/jira/browse/PHOENIX-4397
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.13.0
>        Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
> Fix For: 4.14.0, 4.13.2
>
> Attachments: PHOENIX-4397.patch, PHOENIX-4397_v2.patch
>
>
> See attached unit test.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [VOTE] Release of Apache Phoenix 4.13.1 RC0

[Mujtaba Chohan]

+1.

Checked PHOENIX-4381, PHOENIX-4386 and PHOENIX-4384 that are part of 4.13.1
release.

On Mon, Dec 4, 2017 at 10:40 PM, Thomas D'Silva 
wrote:

> +1
>
> Ran some manual tests using HBase 1.3
>
> On Sat, Dec 2, 2017 at 5:45 AM, Pedro Boado  wrote:
>
> > +1 I've been using branch HBase-1.2 without any issues as base for
> > PHOENIX-4372 and all tests that I've done are correct.
> >
> > On 30 November 2017 at 16:15, Xavier Jodoin  wrote:
> >
> > > +1 The release work perfectly under HBase 1.1
> > >
> > >
> > > On 2017-11-28 13:14, James Taylor  wrote:
> > > > Hello Everyone,>
> > > >
> > > > This is a call for a vote on Apache Phoenix 4.13.0 RC1. This is a
> > patch>
> > > > release of Phoenix 4.13 and is compatible with Apache HBase 0.98,
> 1.1,
> > > 1.2>
> > > > and 1.3. The release includes both a source-only release and a
> > > convenience>
> > > > binary release for each supported HBase version.>
> > > >
> > > > This release has feature parity with supported HBase versions and
> > > includes>
> > > > the following improvements:>
> > > > - Support for HBase 1.1 and 1.2. Future releases of these branches
> will
> > > be>
> > > > done by new release managers.>
> > > > - Include required jars in phoenix server jar for linguistic sort
> > > built-in>
> > > > function [1]>
> > > >
> > > > The source tarball, including signatures, digests, etc can be found
> > at:>
> > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-phoeni
> > > x-4.13.1-HBase-0.98-rc0/src/>
> > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-phoeni
> > > x-4.13.1-HBase-1.1-rc0/src/>
> > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-phoeni
> > > x-4.13.1-HBase-1.2-rc0/src/>
> > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-phoeni
> > > x-4.13.1-HBase-1.3-rc0/src/>
> > > >
> > > > The binary artifacts can be found at:>
> > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-phoeni
> > > x-4.13.1-HBase-0.98-rc0/bin/>
> > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-phoeni
> > > x-4.13.1-HBase-1.1-rc0/bin/>
> > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-phoeni
> > > x-4.13.1-HBase-1.2-rc0/bin/>
> > > > https://dist.apache.org/repos/dist/dev/phoenix/apache-phoeni
> > > x-4.13.1-HBase-1.3-rc0/bin/>
> > > >
> > > > For a complete list of changes, see:>
> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> > > ctId=12315120=12342187>
> > > >
> > > > Release artifacts are signed with the following key:>
> > > > https://people.apache.org/keys/committer/mujtaba.asc>
> > > > https://dist.apache.org/repos/dist/release/phoenix/KEYS>
> > > >
> > > > The hash and tag to be voted upon:>
> > > > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=comm
> > > it;h=ec452ef84d2e976cb7169d4e5e7cf61f3c47f713>
> > > > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
> > > h=refs/tags/v4.13.1-HBase-0.98-rc0>
> > > > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=comm
> > > it;h=9efd7afc7af8072a5302fb8167867cfddb851f3d>
> > > > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
> > > h=refs/tags/v4.13.1-HBase-1.1-rc0>
> > > > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=comm
> > > it;h=17b872cbb0d788c8a033524cc7625d4dd584790b>
> > > > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
> > > h=refs/tags/v4.13.1-HBase-1.2-rc0>
> > > > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=comm
> > > it;h=f232dc971f5714e1e3ea98d43c68073deaa6f058>
> > > > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
> > > h=refs/tags/v4.13.1-HBase-1.3-rc0>
> > > >
> > > > Vote will be open for at least 72 hours. Please vote:>
> > > >
> > > > [ ] +1 approve>
> > > > [ ] +0 no opinion>
> > > > [ ] -1 disapprove (and reason why)>
> > > >
> > > > Thanks,>
> > > > The Apache Phoenix Team>
> > > >
> > > > [1] https://issues.apache.org/jira/browse/PHOENIX-4384>
> > > >
> > >
> >
> >
> >
> > --
> > Un saludo.
> > Pedro Boado.
> >
>

[jira] [Updated] (PHOENIX-4415) Ignore CURRENT_SCN property if set in Pig Storer

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4415:

Attachment: PHOENIX-4415_v3.patch

Removes org.apache.curator.shaded.com.google.common.collect.Sets dependency. 
[~jamestaylor], [~tdsilva]

> Ignore CURRENT_SCN property if set in Pig Storer
> 
>
> Key: PHOENIX-4415
> URL: https://issues.apache.org/jira/browse/PHOENIX-4415
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: James Taylor
> Attachments: PHOENIX-4415.patch, PHOENIX-4415_v2.patch, 
> PHOENIX-4415_v3.patch
>
>
> Phoenix does not support back-in-time writes, so to guard against that we'll 
> remove the CURRENT_SCN property if it's set in the job configuration in 
> PhoenixHBaseStorage.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PHOENIX-4414) Exception while using database metadata commands on tenant specific connection

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4414:

Attachment: PHOENIX-4414.patch

Patch attached. 

FYI [~cody.mar...@gmail.com]

> Exception while using database metadata commands on tenant specific connection
> --
>
> Key: PHOENIX-4414
> URL: https://issues.apache.org/jira/browse/PHOENIX-4414
> Project: Phoenix
>  Issue Type: Bug
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
>Priority: Minor
> Attachments: PHOENIX-4414.patch
>
>
> This is when using tenant specific connection from Sqlline.
> {noformat}
> Error: ERROR 602 (42P00): Syntax error. Missing "LPAREN" at line 2, column 
> 746. (state=42P00,code=602)
> org.apache.phoenix.exception.PhoenixParserException: ERROR 602 (42P00): 
> Syntax error. Missing "LPAREN" at line 2, column 746.
>   at 
> org.apache.phoenix.exception.PhoenixParserException.newException(PhoenixParserException.java:33)
>   at org.apache.phoenix.parse.SQLParser.parseStatement(SQLParser.java:111)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement$PhoenixStatementParser.parseStatement(PhoenixStatement.java:1529)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement.parseStatement(PhoenixStatement.java:1612)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:1653)
>   at 
> org.apache.phoenix.jdbc.PhoenixDatabaseMetaData.getColumns(PhoenixDatabaseMetaData.java:557)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PHOENIX-4414) Exception while using database metadata commands on tenant specific connection

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4414:
---

 Summary: Exception while using database metadata commands on 
tenant specific connection
 Key: PHOENIX-4414
 URL: https://issues.apache.org/jira/browse/PHOENIX-4414
 Project: Phoenix
  Issue Type: Bug
Reporter: Mujtaba Chohan
Assignee: Mujtaba Chohan
Priority: Minor


This is when using tenant specific connection from Sqlline.

{noformat}
Error: ERROR 602 (42P00): Syntax error. Missing "LPAREN" at line 2, column 746. 
(state=42P00,code=602)
org.apache.phoenix.exception.PhoenixParserException: ERROR 602 (42P00): Syntax 
error. Missing "LPAREN" at line 2, column 746.
at 
org.apache.phoenix.exception.PhoenixParserException.newException(PhoenixParserException.java:33)
at org.apache.phoenix.parse.SQLParser.parseStatement(SQLParser.java:111)
at 
org.apache.phoenix.jdbc.PhoenixStatement$PhoenixStatementParser.parseStatement(PhoenixStatement.java:1529)
at 
org.apache.phoenix.jdbc.PhoenixStatement.parseStatement(PhoenixStatement.java:1612)
at 
org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:1653)
at 
org.apache.phoenix.jdbc.PhoenixDatabaseMetaData.getColumns(PhoenixDatabaseMetaData.java:557)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PHOENIX-4397) Incorrect query results when with stats are disabled on a salted table

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4397:

Affects Version/s: 4.13.0

> Incorrect query results when with stats are disabled on a salted table
> --
>
> Key: PHOENIX-4397
> URL: https://issues.apache.org/jira/browse/PHOENIX-4397
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.13.0
>        Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
> Fix For: 4.13.1
>
> Attachments: PHOENIX-4397.patch
>
>
> See attached unit test.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PHOENIX-4397) Incorrect query results when with stats are disabled on a salted table

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4397:

Fix Version/s: 4.13.1

> Incorrect query results when with stats are disabled on a salted table
> --
>
> Key: PHOENIX-4397
> URL: https://issues.apache.org/jira/browse/PHOENIX-4397
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.13.0
>        Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
> Fix For: 4.13.1
>
> Attachments: PHOENIX-4397.patch
>
>
> See attached unit test.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (PHOENIX-4397) Incorrect query results when with stats are disabled on a salted table

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261681#comment-16261681
 ] 

Mujtaba Chohan commented on PHOENIX-4397:
-

[~jamestaylor] Candidate for 4.13.1 as well?

> Incorrect query results when with stats are disabled on a salted table
> --
>
> Key: PHOENIX-4397
> URL: https://issues.apache.org/jira/browse/PHOENIX-4397
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.13.0
>        Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
> Fix For: 4.13.1
>
> Attachments: PHOENIX-4397.patch
>
>
> See attached unit test.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (PHOENIX-4397) Incorrect query results when with stats are disabled on a salted table

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan reassigned PHOENIX-4397:
---

Assignee: Samarth Jain

> Incorrect query results when with stats are disabled on a salted table
> --
>
> Key: PHOENIX-4397
> URL: https://issues.apache.org/jira/browse/PHOENIX-4397
> Project: Phoenix
>  Issue Type: Bug
>    Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
> Attachments: PHOENIX-4397.patch
>
>
> See attached unit test.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PHOENIX-4397) Incorrect query results when with stats are disabled on a salted table

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4397:

Attachment: PHOENIX-4397.patch

> Incorrect query results when with stats are disabled on a salted table
> --
>
> Key: PHOENIX-4397
> URL: https://issues.apache.org/jira/browse/PHOENIX-4397
> Project: Phoenix
>  Issue Type: Bug
>    Reporter: Mujtaba Chohan
> Attachments: PHOENIX-4397.patch
>
>
> See attached unit test.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PHOENIX-4397) Incorrect query results when with stats are disabled on a salted table

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4397:
---

 Summary: Incorrect query results when with stats are disabled on a 
salted table
 Key: PHOENIX-4397
 URL: https://issues.apache.org/jira/browse/PHOENIX-4397
 Project: Phoenix
  Issue Type: Bug
Reporter: Mujtaba Chohan


See attached unit test.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (PHOENIX-4384) Phoenix server jar doesn't include icu4j jars

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255795#comment-16255795
 ] 

Mujtaba Chohan commented on PHOENIX-4384:
-

+1

> Phoenix server jar doesn't include icu4j jars
> -
>
> Key: PHOENIX-4384
> URL: https://issues.apache.org/jira/browse/PHOENIX-4384
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.13.0
>Reporter: Shehzaad Nakhoda
>Assignee: Shehzaad Nakhoda
> Fix For: 4.13.0
>
> Attachments: PHOENIX-4384_v1.patch
>
>
> The phoenix server "shaded" jar is supposed to include all? its dependencies. 
> However icu4j is missing. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [VOTE] Release of Apache Phoenix 4.13.0 RC1

[Mujtaba Chohan]

+1.

Verified performance and backward compat. with 4.10/11/12.

On Tue, Nov 7, 2017 at 2:50 PM, Andrew Purtell  wrote:

> +1
>
> Checked sums and signatures: ok
> RAT check passes: ok (8u131) [1]
> Built from source: ok (8u131) [1]
> Unit tests pass: ok (8u131) [2]
>
>
> 1. There are some Maven warnings that should be fixed, but are not release
> blockers. "Reporting configuration should be done in  section,
> not in maven-site-plugin  as reportPlugins parameter." Maven
> 3.5.0.
>
> 2. PartialIndexRebuilderIT.testConcurrentUpsertsWithRebuild ran out of
> time
> when executed with other tests, but passed when run standalone.
>
>
> On Mon, Nov 6, 2017 at 3:47 PM, James Taylor 
> wrote:
>
> > Hello Everyone,
> >
> > This is a call for a vote on Apache Phoenix 4.13.0 RC1. This is the next
> > minor release of Phoenix 4, compatible with Apache HBase 0.98 and 1.3.
> The
> > release includes both a source-only release and a convenience binary
> > release for each supported HBase version. The previous RC was sunk due to
> > PHOENIX-4351 which is now fixed.
> >
> > This release has feature parity with supported HBase versions and
> includes
> > the following improvements:
> > - Critical bug fix to prevent snapshot creation of SYSTEM.CATALOG when
> > connecting [1]
> > - Numerous bug fixes around handling of row deletion [2][3][4][5]
> > - Improvements to statistics collection [6][7][8][9]
> > - New COLLATION_KEY built-in function for linguistic sort [10]
> >
> > The source tarball, including signatures, digests, etc can be found at:
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-phoeni
> > x-4.13.0-HBase-0.98-rc1/src/
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-phoeni
> > x-4.13.0-HBase-1.3-rc1/src/
> >
> > The binary artifacts can be found at:
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-phoeni
> > x-4.13.0-HBase-0.98-rc1/bin/
> > https://dist.apache.org/repos/dist/dev/phoenix/apache-phoeni
> > x-4.13.0-HBase-1.3-rc1/bin/
> >
> > For a complete list of changes, see:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> > ctId=12315120=12341710
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/mujtaba.asc
> > https://dist.apache.org/repos/dist/release/phoenix/KEYS
> >
> > The hash and tag to be voted upon:
> > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=comm
> > it;h=8b7e12414400c997d5993fb55586bfcc2f56d217
> > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
> > h=refs/tags/v4.13.0-HBase-0.98-rc1
> > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=comm
> > it;h=4a1f0df6143ba705a48b5051aee52dab158afe8d
> > https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
> > h=refs/tags/v4.13.0-HBase-1.3-rc1
> >
> > Vote will be open for at least 72 hours. Please vote:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> > Thanks,
> > The Apache Phoenix Team
> >
> > [1] https://issues.apache.org/jira/browse/PHOENIX-4335
> > [2] https://issues.apache.org/jira/browse/PHOENIX-4280
> > [3] https://issues.apache.org/jira/browse/PHOENIX-4290
> > [4] https://issues.apache.org/jira/browse/PHOENIX-4348
> > [5] https://issues.apache.org/jira/browse/PHOENIX-4277
> > [6] https://issues.apache.org/jira/browse/PHOENIX-3368
> > [7] https://issues.apache.org/jira/browse/PHOENIX-4287
> > [8] https://issues.apache.org/jira/browse/PHOENIX-4289
> > [9] https://issues.apache.org/jira/browse/PHOENIX-4343
> > [10] https://issues.apache.org/jira/browse/PHOENIX-4237
> >
>

Re: [VOTE] Release of Apache Phoenix 4.13.0 RC0

[Mujtaba Chohan]

+1

Compared/verified performance and backward compatibility.

On Mon, Nov 6, 2017 at 9:18 AM, Josh Elser  wrote:

> Thanks for the correction, James. This wasn't added to
> dependencyManagement, so I missed it.
>
> The Salesforce copyright notice (https://github.com/salesforce
> /i18n-util/blob/master/LICENSE.txt) should be propagated to our
> binary-release's NOTICE file (dev/release_files/NOTICE) and the project
> name should be listed with the rest of the 3-clause BSD-licensed
> dependencies we bundle in our LICENSE file (also in dev/release_files).
>
> Three small things to fix for this -- if nothing else is found wrong in
> rc0, (IMO) fix it for the next release.
>
>
> On 11/3/17 11:57 PM, James Taylor wrote:
>
>> Thanks for the vote, Josh, but FYI there is a new dependency
>> with com.salesforce.i18n:i18n-util that went in with PHOENIX-4237.
>>
>> On Fri, Nov 3, 2017 at 8:23 PM, Josh Elser  wrote:
>>
>> +1 (binding)
>>>
>>> * Can build from source and run unit tests
>>> * No new deps since 4.12 (implies L is still good)
>>> * 4.13 tags are deployed and match
>>> * No unexpected files in src releases
>>>
>>>
>>> On 11/3/17 6:21 PM, James Taylor wrote:
>>>
>>> Hello Everyone,

 This is a call for a vote on Apache Phoenix 4.13.0 RC0. This is the next
 minor release of Phoenix 4, compatible with Apache HBase 0.98 and 1.3.
 The
 release includes both a source-only release and a convenience binary
 release for each supported HBase version.

 This release has feature parity with supported HBase versions and
 includes
 the following improvements:
 - Critical bug fix to prevent snapshot creation of SYSTEM.CATALOG when
 connecting [1]
 - Numerous bug fixes around handling of row deletion [2][3][4][5]
 - Improvements to statistics collection [6][7][8][9]
 - New COLLATION_KEY built-in function for linguistic sort [10]

 The source tarball, including signatures, digests, etc can be found at:
 https://dist.apache.org/repos/dist/dev/phoenix/apache-phoeni
 x-4.13.0-HBase-0.98-rc0/src/
 https://dist.apache.org/repos/dist/dev/phoenix/apache-phoeni
 x-4.13.0-HBase-1.3-rc0/src/

 The binary artifacts can be found at:
 https://dist.apache.org/repos/dist/dev/phoenix/apache-phoeni
 x-4.13.0-HBase-0.98-rc0/bin/
 https://dist.apache.org/repos/dist/dev/phoenix/apache-phoeni
 x-4.13.0-HBase-1.3-rc0/bin/

 For a complete list of changes, see:
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
 ctId=12315120=12341710

 Release artifacts are signed with the following key:
 https://people.apache.org/keys/committer/mujtaba.asc
 https://dist.apache.org/repos/dist/release/phoenix/KEYS

 The hash and tag to be voted upon:
 https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=comm
 it;h=7e795ac67fd21bd48f49acda3327c83d369aead4
 https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
 h=refs/tags/v4.13.0-HBase-0.98-rc0
 https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=comm
 it;h=a09cea6bfb94edd95ce06aa2cb7f229227db5666
 https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
 h=refs/tags/v4.13.0-HBase-1.3-rc0
 The hash and tag to be voted upon:
 https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=comm
 it;h=13a7f97b49704642d67481c58a118a68c2e4c2e5
 https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
 h=refs/tags/v4.12.0-HBase-0.98-rc0
 https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=comm
 it;h=e40bbfff1150e56e1ecb7cd22c49cee298496c2b
 https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
 h=refs/tags/v4.12.0-HBase-1.1-rc0
 https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=comm
 it;h=d79dd50ff732f2673e1414d970cd4742e2c135de
 https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
 h=refs/tags/v4.12.0-HBase-1.2-rc0
 https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=comm
 it;h=f0bc4cdb5bbf96b316c78cc816400b04f63e911b
 https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;
 h=refs/tags/v4.12.0-HBase-1.3-rc0

 Vote will be open for at least 72 hours. Please vote:

 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)

 Thanks,
 The Apache Phoenix Team

 [1] https://issues.apache.org/jira/browse/PHOENIX-4335
 [2] https://issues.apache.org/jira/browse/PHOENIX-4280
 [3] https://issues.apache.org/jira/browse/PHOENIX-4290
 [4] https://issues.apache.org/jira/browse/PHOENIX-4348
 [5] https://issues.apache.org/jira/browse/PHOENIX-4277
 [6] https://issues.apache.org/jira/browse/PHOENIX-3368
 [7] https://issues.apache.org/jira/browse/PHOENIX-4287
 [8] https://issues.apache.org/jira/browse/PHOENIX-4289
 [9] https://issues.apache.org/jira/browse/PHOENIX-4343
 [10] 

[jira] [Resolved] (PHOENIX-4291) Merge release script for mac and linux

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan resolved PHOENIX-4291.
-
Resolution: Fixed

> Merge release script for mac and linux
> --
>
> Key: PHOENIX-4291
> URL: https://issues.apache.org/jira/browse/PHOENIX-4291
> Project: Phoenix
>  Issue Type: Improvement
>Affects Versions: 4.12.0
>        Reporter: Mujtaba Chohan
>    Assignee: Mujtaba Chohan
> Fix For: 4.12.1
>
> Attachments: PHOENIX-4291.patch
>
>
> Merging make_rc.sh and make_rc_on_mac.sh to make_rc_sh. This is based on 
> changes that [~jamestaylor] had in place to execute the script on a Mac.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (PHOENIX-4287) Incorrect aggregate query results when stats are disable for parallelization

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16236574#comment-16236574
 ] 

Mujtaba Chohan commented on PHOENIX-4287:
-

Alter on index leads to:
{noformat}
ERROR 1010 (42M01): Not allowed to mutate table.
{noformat}

> Incorrect aggregate query results when stats are disable for parallelization
> 
>
> Key: PHOENIX-4287
> URL: https://issues.apache.org/jira/browse/PHOENIX-4287
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.12.0
> Environment: HBase 1.3.1
>    Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
>Priority: Major
>  Labels: localIndex
> Fix For: 4.13.0, 4.12.1
>
> Attachments: PHOENIX-4287.patch, PHOENIX-4287_addendum.patch, 
> PHOENIX-4287_addendum2.patch, PHOENIX-4287_addendum3.patch, 
> PHOENIX-4287_addendum4.patch, PHOENIX-4287_v2.patch, PHOENIX-4287_v3.patch, 
> PHOENIX-4287_v3_wip.patch, PHOENIX-4287_v4.patch
>
>
> With {{phoenix.use.stats.parallelization}} set to {{false}}, aggregate query 
> returns incorrect results when stats are available.
> With local index and stats disabled for parallelization:
> {noformat}
> explain select count(*) from TABLE_T;
> +---+-++---+
> | PLAN
>   | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO |
> +---+-++---+
> | CLIENT 0-CHUNK 332170 ROWS 625043899 BYTES PARALLEL 0-WAY RANGE SCAN OVER 
> TABLE_T [1]  | 625043899   | 332170 | 150792825 |
> | SERVER FILTER BY FIRST KEY ONLY 
>   | 625043899   | 332170 | 150792825 |
> | SERVER AGGREGATE INTO SINGLE ROW
>   | 625043899   | 332170 | 150792825 |
> +---+-++---+
> select count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 0 |
> +---+
> {noformat}
> Using data table
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-+++
> |   PLAN  
>  | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO_TS   |
> +--+-+++
> | CLIENT 2-CHUNK 332151 ROWS 438492470 BYTES PARALLEL 1-WAY FULL SCAN OVER 
> TABLE_T  | 438492470   | 332151 | 1507928257617  |
> | SERVER FILTER BY FIRST KEY ONLY 
>  | 438492470   | 332151 | 1507928257617  |
> | SERVER AGGREGATE INTO SINGLE ROW
>  | 438492470   | 332151 | 1507928257617  |
> +--+-+++
> select /*+NO_INDEX*/ count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 14|
> +---+
> {noformat}
> Without stats available, results are correct:
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-++--+
> | PLAN | 
> EST_BYTES_READ  | EST_ROWS_READ  | EST_INFO_TS  |
> +--+-++--+
> | CLIENT 2-CHUNK PARALLEL 1-WAY FULL SCAN OVER TABLE_T  | null| 
> null   | null |
> | SERVER FILTER BY FIRST KEY ONLY  | null 
>| null   | null |
> | SERVER AGGREGATE INTO SINGLE ROW  

[jira] [Commented] (PHOENIX-4287) Incorrect aggregate query results when stats are disable for parallelization

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16236498#comment-16236498
 ] 

Mujtaba Chohan commented on PHOENIX-4287:
-

Just figured that out as well :) That index was created with previous version 
and it had {{USE_STATS_FOR_PARALLELIZATION}} set to true causing index to use 
parallelization. 

Here's a case that still doesn't work with table created with latest version:
Global {{USE_STATS_FOR_PARALLELIZATION}} is set to *false*.
Table and global index created without setting parallelization.
Table parallelization is set to *true* ALTER ...SET 
USE_STATS_FOR_PARALLELIZATION=true. Verified in SYSTEM.CATALOG as well as it is 
set for base table only.
Parallelization is *not* used for queries when they get executed against 
*index*, parallelization is correctly used for base table.




> Incorrect aggregate query results when stats are disable for parallelization
> 
>
> Key: PHOENIX-4287
> URL: https://issues.apache.org/jira/browse/PHOENIX-4287
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.12.0
> Environment: HBase 1.3.1
>    Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
>Priority: Major
>  Labels: localIndex
> Fix For: 4.13.0, 4.12.1
>
> Attachments: PHOENIX-4287.patch, PHOENIX-4287_addendum.patch, 
> PHOENIX-4287_addendum2.patch, PHOENIX-4287_addendum3.patch, 
> PHOENIX-4287_addendum4.patch, PHOENIX-4287_v2.patch, PHOENIX-4287_v3.patch, 
> PHOENIX-4287_v3_wip.patch, PHOENIX-4287_v4.patch
>
>
> With {{phoenix.use.stats.parallelization}} set to {{false}}, aggregate query 
> returns incorrect results when stats are available.
> With local index and stats disabled for parallelization:
> {noformat}
> explain select count(*) from TABLE_T;
> +---+-++---+
> | PLAN
>   | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO |
> +---+-++---+
> | CLIENT 0-CHUNK 332170 ROWS 625043899 BYTES PARALLEL 0-WAY RANGE SCAN OVER 
> TABLE_T [1]  | 625043899   | 332170 | 150792825 |
> | SERVER FILTER BY FIRST KEY ONLY 
>   | 625043899   | 332170 | 150792825 |
> | SERVER AGGREGATE INTO SINGLE ROW
>   | 625043899   | 332170 | 150792825 |
> +---+-++---+
> select count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 0 |
> +---+
> {noformat}
> Using data table
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-+++
> |   PLAN  
>  | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO_TS   |
> +--+-+++
> | CLIENT 2-CHUNK 332151 ROWS 438492470 BYTES PARALLEL 1-WAY FULL SCAN OVER 
> TABLE_T  | 438492470   | 332151 | 1507928257617  |
> | SERVER FILTER BY FIRST KEY ONLY 
>  | 438492470   | 332151 | 1507928257617  |
> | SERVER AGGREGATE INTO SINGLE ROW
>  | 438492470   | 332151 | 1507928257617  |
> +--+-+++
> select /*+NO_INDEX*/ count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 14|
> +---+
> {noformat}
> Without stats available, results are correct:
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +---

[jira] [Comment Edited] (PHOENIX-4287) Incorrect aggregate query results when stats are disable for parallelization

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16236431#comment-16236431
 ] 

Mujtaba Chohan edited comment on PHOENIX-4287 at 11/2/17 7:24 PM:
--

[~jamestaylor] At table creation time I didn't set 
USE_STATS_FOR_PARALLELIZATION and as global setting it's set to false. Later I 
turn it off as well with ALTER statement. Index is global.


was (Author: mujtabachohan):
[~jamestaylor] At table creation time I didn't set 
USE_STATS_FOR_PARALLELIZATION and as global setting it's set to false. Index is 
global.

> Incorrect aggregate query results when stats are disable for parallelization
> 
>
> Key: PHOENIX-4287
> URL: https://issues.apache.org/jira/browse/PHOENIX-4287
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.12.0
> Environment: HBase 1.3.1
>    Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
>Priority: Major
>  Labels: localIndex
> Fix For: 4.13.0, 4.12.1
>
> Attachments: PHOENIX-4287.patch, PHOENIX-4287_addendum.patch, 
> PHOENIX-4287_addendum2.patch, PHOENIX-4287_addendum3.patch, 
> PHOENIX-4287_addendum4.patch, PHOENIX-4287_v2.patch, PHOENIX-4287_v3.patch, 
> PHOENIX-4287_v3_wip.patch, PHOENIX-4287_v4.patch
>
>
> With {{phoenix.use.stats.parallelization}} set to {{false}}, aggregate query 
> returns incorrect results when stats are available.
> With local index and stats disabled for parallelization:
> {noformat}
> explain select count(*) from TABLE_T;
> +---+-++---+
> | PLAN
>   | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO |
> +---+-++---+
> | CLIENT 0-CHUNK 332170 ROWS 625043899 BYTES PARALLEL 0-WAY RANGE SCAN OVER 
> TABLE_T [1]  | 625043899   | 332170 | 150792825 |
> | SERVER FILTER BY FIRST KEY ONLY 
>   | 625043899   | 332170 | 150792825 |
> | SERVER AGGREGATE INTO SINGLE ROW
>   | 625043899   | 332170 | 150792825 |
> +---+-++---+
> select count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 0 |
> +---+
> {noformat}
> Using data table
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-+++
> |   PLAN  
>  | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO_TS   |
> +--+-+++
> | CLIENT 2-CHUNK 332151 ROWS 438492470 BYTES PARALLEL 1-WAY FULL SCAN OVER 
> TABLE_T  | 438492470   | 332151 | 1507928257617  |
> | SERVER FILTER BY FIRST KEY ONLY 
>  | 438492470   | 332151 | 1507928257617  |
> | SERVER AGGREGATE INTO SINGLE ROW
>  | 438492470   | 332151 | 1507928257617  |
> +--+-+++
> select /*+NO_INDEX*/ count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 14|
> +---+
> {noformat}
> Without stats available, results are correct:
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-++--+
> | PLAN | 
> EST_BYTES_READ  | EST_ROWS_READ  | EST_INFO_TS  |
> +--+-++--+
> | CLIENT 

[jira] [Commented] (PHOENIX-4287) Incorrect aggregate query results when stats are disable for parallelization

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16236431#comment-16236431
 ] 

Mujtaba Chohan commented on PHOENIX-4287:
-

[~jamestaylor] At table creation time I didn't set 
USE_STATS_FOR_PARALLELIZATION and as global setting it's set to false. Index is 
global.

> Incorrect aggregate query results when stats are disable for parallelization
> 
>
> Key: PHOENIX-4287
> URL: https://issues.apache.org/jira/browse/PHOENIX-4287
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.12.0
> Environment: HBase 1.3.1
>    Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
>Priority: Major
>  Labels: localIndex
> Fix For: 4.13.0, 4.12.1
>
> Attachments: PHOENIX-4287.patch, PHOENIX-4287_addendum.patch, 
> PHOENIX-4287_addendum2.patch, PHOENIX-4287_addendum3.patch, 
> PHOENIX-4287_addendum4.patch, PHOENIX-4287_v2.patch, PHOENIX-4287_v3.patch, 
> PHOENIX-4287_v3_wip.patch, PHOENIX-4287_v4.patch
>
>
> With {{phoenix.use.stats.parallelization}} set to {{false}}, aggregate query 
> returns incorrect results when stats are available.
> With local index and stats disabled for parallelization:
> {noformat}
> explain select count(*) from TABLE_T;
> +---+-++---+
> | PLAN
>   | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO |
> +---+-++---+
> | CLIENT 0-CHUNK 332170 ROWS 625043899 BYTES PARALLEL 0-WAY RANGE SCAN OVER 
> TABLE_T [1]  | 625043899   | 332170 | 150792825 |
> | SERVER FILTER BY FIRST KEY ONLY 
>   | 625043899   | 332170 | 150792825 |
> | SERVER AGGREGATE INTO SINGLE ROW
>   | 625043899   | 332170 | 150792825 |
> +---+-++---+
> select count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 0 |
> +---+
> {noformat}
> Using data table
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-+++
> |   PLAN  
>  | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO_TS   |
> +--+-+++
> | CLIENT 2-CHUNK 332151 ROWS 438492470 BYTES PARALLEL 1-WAY FULL SCAN OVER 
> TABLE_T  | 438492470   | 332151 | 1507928257617  |
> | SERVER FILTER BY FIRST KEY ONLY 
>  | 438492470   | 332151 | 1507928257617  |
> | SERVER AGGREGATE INTO SINGLE ROW
>  | 438492470   | 332151 | 1507928257617  |
> +--+-+++
> select /*+NO_INDEX*/ count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 14|
> +---+
> {noformat}
> Without stats available, results are correct:
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-++--+
> | PLAN | 
> EST_BYTES_READ  | EST_ROWS_READ  | EST_INFO_TS  |
> +--+-++--+
> | CLIENT 2-CHUNK PARALLEL 1-WAY FULL SCAN OVER TABLE_T  | null| 
> null   | null |
> | SERVER FILTER BY FIRST KEY ONLY  | null 
>| null   | null |
> | SERVER AGGREGATE INTO SINGLE ROW  

[jira] [Comment Edited] (PHOENIX-4287) Incorrect aggregate query results when stats are disable for parallelization

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16236356#comment-16236356
 ] 

Mujtaba Chohan edited comment on PHOENIX-4287 at 11/2/17 6:39 PM:
--

[~samarthjain] With {{ALTER ...SET USE_STATS_FOR_PARALLELIZATION=false}} on 
base table and also config set to false globally, stats are correctly not used 
for parallelization when query runs on base table however for index table they 
are still used. See explain plan below. This is with 
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=6e80b0fb0386c48c0837d73d72dd4aee1ca15c4a

{noformat}
ALTER TABLE T SET USE_STATS_FOR_PARALLELIZATION=false;
explain select count(*) from T;
+--+-+++
|   PLAN
   | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO_TS   |
+--+-+++
| CLIENT 11277-CHUNK 1161114 ROWS 63050353 BYTES PARALLEL 1-WAY FULL SCAN OVER 
T_IDX  | 63050353| 1161114| 1509646993152  |
| SERVER FILTER BY FIRST KEY ONLY   
   | 63050353| 1161114| 1509646993152  |
| SERVER AGGREGATE INTO SINGLE ROW  
   | 63050353| 1161114| 1509646993152  |
+--+-+++
{noformat}


was (Author: mujtabachohan):
[~samarthjain] With {{ALTER ...SET USE_STATS_FOR_PARALLELIZATION=false}} on 
base table and also config set to false globally, stats are correctly not used 
for parallelization when query runs on base table however on for index it is 
still used. See explain plan below. This is with 
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=6e80b0fb0386c48c0837d73d72dd4aee1ca15c4a

{noformat}
ALTER TABLE T SET USE_STATS_FOR_PARALLELIZATION=false;
explain select count(*) from T;
+--+-+++
|   PLAN
   | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO_TS   |
+--+-+++
| CLIENT 11277-CHUNK 1161114 ROWS 63050353 BYTES PARALLEL 1-WAY FULL SCAN OVER 
T_IDX  | 63050353| 1161114| 1509646993152  |
| SERVER FILTER BY FIRST KEY ONLY   
   | 63050353| 1161114| 1509646993152  |
| SERVER AGGREGATE INTO SINGLE ROW  
   | 63050353| 1161114| 1509646993152  |
+--+-+++
{noformat}

> Incorrect aggregate query results when stats are disable for parallelization
> 
>
> Key: PHOENIX-4287
> URL: https://issues.apache.org/jira/browse/PHOENIX-4287
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.12.0
> Environment: HBase 1.3.1
>    Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
>Priority: Major
>  Labels: localIndex
> Fix For: 4.13.0, 4.12.1
>
> Attachments: PHOENIX-4287.patch, PHOENIX-4287_addendum.patch, 
> PHOENIX-4287_addendum2.patch, PHOENIX-4287_addendum3.patch, 
> PHOENIX-4287_addendum4.patch, PHOENIX-4287_v2.patch, PHOENIX-4287_v3.patch, 
> PHOENIX-4287_v3_wip.patch, PHOENIX-4287_v4.patch
>
>
> With {{phoenix.use.stats.parallelization}} set to {{false}}, aggregate query 
> returns incorrect results when stats are available.
> With local index and stats disabled for parallelization:
> {noformat}
> explain select count(*) from TABLE_T;
> +---+-++---+
> | PLAN
>   | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO |
> +---+-++---+
> | CLIENT 0-CHUNK 332170 ROWS 625043899 BYTES PARALLEL 0-WAY RANGE SCAN OVER 
> 

[jira] [Commented] (PHOENIX-4287) Incorrect aggregate query results when stats are disable for parallelization

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16236356#comment-16236356
 ] 

Mujtaba Chohan commented on PHOENIX-4287:
-

[~samarthjain] With {{ALTER ...SET USE_STATS_FOR_PARALLELIZATION=false}} on 
base table and also config set to false globally, stats are correctly not used 
for parallelization when query runs on base table however on for index it is 
still used. See explain plan below. This is with 
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=6e80b0fb0386c48c0837d73d72dd4aee1ca15c4a

{noformat}
ALTER TABLE T SET USE_STATS_FOR_PARALLELIZATION=false;
explain select count(*) from T;
+--+-+++
|   PLAN
   | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO_TS   |
+--+-+++
| CLIENT 11277-CHUNK 1161114 ROWS 63050353 BYTES PARALLEL 1-WAY FULL SCAN OVER 
T_IDX  | 63050353| 1161114| 1509646993152  |
| SERVER FILTER BY FIRST KEY ONLY   
   | 63050353| 1161114| 1509646993152  |
| SERVER AGGREGATE INTO SINGLE ROW  
   | 63050353| 1161114| 1509646993152  |
+--+-+++
{noformat}

> Incorrect aggregate query results when stats are disable for parallelization
> 
>
> Key: PHOENIX-4287
> URL: https://issues.apache.org/jira/browse/PHOENIX-4287
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.12.0
> Environment: HBase 1.3.1
>    Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
>Priority: Major
>  Labels: localIndex
> Fix For: 4.13.0, 4.12.1
>
> Attachments: PHOENIX-4287.patch, PHOENIX-4287_addendum.patch, 
> PHOENIX-4287_addendum2.patch, PHOENIX-4287_addendum3.patch, 
> PHOENIX-4287_addendum4.patch, PHOENIX-4287_v2.patch, PHOENIX-4287_v3.patch, 
> PHOENIX-4287_v3_wip.patch, PHOENIX-4287_v4.patch
>
>
> With {{phoenix.use.stats.parallelization}} set to {{false}}, aggregate query 
> returns incorrect results when stats are available.
> With local index and stats disabled for parallelization:
> {noformat}
> explain select count(*) from TABLE_T;
> +---+-++---+
> | PLAN
>   | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO |
> +---+-++---+
> | CLIENT 0-CHUNK 332170 ROWS 625043899 BYTES PARALLEL 0-WAY RANGE SCAN OVER 
> TABLE_T [1]  | 625043899   | 332170 | 150792825 |
> | SERVER FILTER BY FIRST KEY ONLY 
>   | 625043899   | 332170 | 150792825 |
> | SERVER AGGREGATE INTO SINGLE ROW
>   | 625043899   | 332170 | 150792825 |
> +---+-++---+
> select count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 0 |
> +---+
> {noformat}
> Using data table
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-+++
> |   PLAN  
>  | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO_TS   |
> +--+-+++
> | CLIENT 2-CHUNK 332151 ROWS 438492470 BYTES PARALLEL 1-WAY FULL SCAN OVER 
> TABLE_T  | 438492470   | 332151 | 1507928257617  |
> | SERVER FILTER BY FIRST KEY ONLY 
>  | 438492470   |

[jira] [Commented] (PHOENIX-4287) Incorrect aggregate query results when stats are disable for parallelization

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16234614#comment-16234614
 ] 

Mujtaba Chohan commented on PHOENIX-4287:
-

It's an aggregate query on a table. With {{ALTER ...SET 
USE_STATS_FOR_PARALLELIZATION=false}} it works fine. So the issue is when it's 
set globally in hbase-site.xml.

> Incorrect aggregate query results when stats are disable for parallelization
> 
>
> Key: PHOENIX-4287
> URL: https://issues.apache.org/jira/browse/PHOENIX-4287
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.12.0
> Environment: HBase 1.3.1
>    Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
>Priority: Major
>  Labels: localIndex
> Fix For: 4.13.0, 4.12.1
>
> Attachments: PHOENIX-4287.patch, PHOENIX-4287_v2.patch, 
> PHOENIX-4287_v3.patch, PHOENIX-4287_v3_wip.patch, PHOENIX-4287_v4.patch
>
>
> With {{phoenix.use.stats.parallelization}} set to {{false}}, aggregate query 
> returns incorrect results when stats are available.
> With local index and stats disabled for parallelization:
> {noformat}
> explain select count(*) from TABLE_T;
> +---+-++---+
> | PLAN
>   | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO |
> +---+-++---+
> | CLIENT 0-CHUNK 332170 ROWS 625043899 BYTES PARALLEL 0-WAY RANGE SCAN OVER 
> TABLE_T [1]  | 625043899   | 332170 | 150792825 |
> | SERVER FILTER BY FIRST KEY ONLY 
>   | 625043899   | 332170 | 150792825 |
> | SERVER AGGREGATE INTO SINGLE ROW
>   | 625043899   | 332170 | 150792825 |
> +---+-++---+
> select count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 0 |
> +---+
> {noformat}
> Using data table
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-+++
> |   PLAN  
>  | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO_TS   |
> +--+-+++
> | CLIENT 2-CHUNK 332151 ROWS 438492470 BYTES PARALLEL 1-WAY FULL SCAN OVER 
> TABLE_T  | 438492470   | 332151 | 1507928257617  |
> | SERVER FILTER BY FIRST KEY ONLY 
>  | 438492470   | 332151 | 1507928257617  |
> | SERVER AGGREGATE INTO SINGLE ROW
>  | 438492470   | 332151 | 1507928257617  |
> +--+-+++
> select /*+NO_INDEX*/ count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 14|
> +---+
> {noformat}
> Without stats available, results are correct:
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-++--+
> | PLAN | 
> EST_BYTES_READ  | EST_ROWS_READ  | EST_INFO_TS  |
> +--+-++--+
> | CLIENT 2-CHUNK PARALLEL 1-WAY FULL SCAN OVER TABLE_T  | null| 
> null   | null |
> | SERVER FILTER BY FIRST KEY ONLY  | null 
>| null   | null |
> | SERVER AGGREGATE INTO SINGLE ROW | null 
>| null   | null |
&

[jira] [Commented] (PHOENIX-4287) Incorrect aggregate query results when stats are disable for parallelization

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16234571#comment-16234571
 ] 

Mujtaba Chohan commented on PHOENIX-4287:
-

[~samarthjain] With stats disabled for parallelization, queue fills up for 
table with large number of stats:
{noformat}
Error: Task 
org.apache.phoenix.job.JobManager$InstrumentedJobFutureTask@309028af rejected 
from org.apache.phoenix.job.JobManager$1@724c5cbe[Running, pool size = 33, 
active threads = 33, queued tasks = 4998, completed tasks = 1302] 
(state=08000,code=101)
{noformat}

> Incorrect aggregate query results when stats are disable for parallelization
> 
>
> Key: PHOENIX-4287
> URL: https://issues.apache.org/jira/browse/PHOENIX-4287
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.12.0
> Environment: HBase 1.3.1
>    Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
>Priority: Major
>  Labels: localIndex
> Fix For: 4.13.0, 4.12.1
>
> Attachments: PHOENIX-4287.patch, PHOENIX-4287_v2.patch, 
> PHOENIX-4287_v3.patch, PHOENIX-4287_v3_wip.patch, PHOENIX-4287_v4.patch
>
>
> With {{phoenix.use.stats.parallelization}} set to {{false}}, aggregate query 
> returns incorrect results when stats are available.
> With local index and stats disabled for parallelization:
> {noformat}
> explain select count(*) from TABLE_T;
> +---+-++---+
> | PLAN
>   | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO |
> +---+-++---+
> | CLIENT 0-CHUNK 332170 ROWS 625043899 BYTES PARALLEL 0-WAY RANGE SCAN OVER 
> TABLE_T [1]  | 625043899   | 332170 | 150792825 |
> | SERVER FILTER BY FIRST KEY ONLY 
>   | 625043899   | 332170 | 150792825 |
> | SERVER AGGREGATE INTO SINGLE ROW
>   | 625043899   | 332170 | 150792825 |
> +---+-++---+
> select count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 0 |
> +---+
> {noformat}
> Using data table
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-+++
> |   PLAN  
>  | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO_TS   |
> +--+-+++
> | CLIENT 2-CHUNK 332151 ROWS 438492470 BYTES PARALLEL 1-WAY FULL SCAN OVER 
> TABLE_T  | 438492470   | 332151 | 1507928257617  |
> | SERVER FILTER BY FIRST KEY ONLY 
>  | 438492470   | 332151 | 1507928257617  |
> | SERVER AGGREGATE INTO SINGLE ROW
>  | 438492470   | 332151 | 1507928257617  |
> +--+-+++
> select /*+NO_INDEX*/ count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 14|
> +---+
> {noformat}
> Without stats available, results are correct:
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-++--+
> | PLAN | 
> EST_BYTES_READ  | EST_ROWS_READ  | EST_INFO_TS  |
> +--+-++--+
> | CLIENT 2-CHUNK PARALLEL 1-WAY FULL SCAN OVER TABLE_T  | null| 
> null   | null |
> | SERVER FILTER BY F

[jira] [Commented] (PHOENIX-4334) Unable to update stats on views that reside on separate regions before phoenix.stats.updateFrequency has elapsed

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16234490#comment-16234490
 ] 

Mujtaba Chohan commented on PHOENIX-4334:
-

So shouldn't we just disallow collection of stats at tenant/view level since 
this will mean that stats for all other views are invalid apart from the one 
that originated the stats collection call as they will report inaccurate 
byte/row count while stats update timestamp for all views will report last 
updated time being current.

FYI [~cody.mar...@gmail.com]

> Unable to update stats on views that reside on separate regions before 
> phoenix.stats.updateFrequency has elapsed
> 
>
> Key: PHOENIX-4334
> URL: https://issues.apache.org/jira/browse/PHOENIX-4334
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.12.0
>    Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
>Priority: Major
>
> Consider multiple tenant views that all reside on unique region/region 
> servers. Updating stats on any one of the view causes other views to report 
> estimated stats last update time as current resulting in stats command 
> getting ignored for other views till {{phoenix.stats.updateFrequency}} has 
> elapsed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (PHOENIX-4335) System catalog snapshot created each time a new connection is created

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225876#comment-16225876
 ] 

Mujtaba Chohan commented on PHOENIX-4335:
-

This affects 4.12.0 release as well.

> System catalog snapshot created each time a new connection is created
> -
>
> Key: PHOENIX-4335
> URL: https://issues.apache.org/jira/browse/PHOENIX-4335
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.12.0
>        Reporter: Mujtaba Chohan
>
> With current head of 4.x, System Catalog snapshot is created on each new 
> connection.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PHOENIX-4335) System catalog snapshot created each time a new connection is created

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4335:

Affects Version/s: 4.12.0

> System catalog snapshot created each time a new connection is created
> -
>
> Key: PHOENIX-4335
> URL: https://issues.apache.org/jira/browse/PHOENIX-4335
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.12.0
>        Reporter: Mujtaba Chohan
>
> With current head of 4.x, System Catalog snapshot is created on each new 
> connection.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PHOENIX-4335) System catalog snapshot created each time a new connection is created

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4335:
---

 Summary: System catalog snapshot created each time a new 
connection is created
 Key: PHOENIX-4335
 URL: https://issues.apache.org/jira/browse/PHOENIX-4335
 Project: Phoenix
  Issue Type: Bug
Reporter: Mujtaba Chohan


With current head of 4.x, System Catalog snapshot is created on each new 
connection.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PHOENIX-4334) Unable to update stats on views that reside on separate regions before phoenix.stats.updateFrequency has elapsed

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4334:
---

 Summary: Unable to update stats on views that reside on separate 
regions before phoenix.stats.updateFrequency has elapsed
 Key: PHOENIX-4334
 URL: https://issues.apache.org/jira/browse/PHOENIX-4334
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.12.0
Reporter: Mujtaba Chohan
Assignee: Samarth Jain


Consider multiple tenant views that all reside on unique region/region servers. 
Updating stats on any one of the view causes other views to report estimated 
stats last update time as current resulting in stats command getting ignored 
for other views till {{phoenix.stats.updateFrequency}} has elapsed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PHOENIX-4333) Stats - Incorrect estimate when stats are updated on a tenant specific view

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4333:
---

 Summary: Stats - Incorrect estimate when stats are updated on a 
tenant specific view
 Key: PHOENIX-4333
 URL: https://issues.apache.org/jira/browse/PHOENIX-4333
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.12.0
Reporter: Mujtaba Chohan
Assignee: Samarth Jain


Consider two tenants A, B with tenant specific view on 2 separate 
regions/region servers.

{noformat}
Region 1 keys:
A,1
A,2
B,1
Region 2 keys:
B,2
B,3
{noformat}

When stats are updated on tenant A view. Querying stats on tenant B view yield 
partial results (only contains stats for B,1) which are incorrect even though 
it shows updated timestamp as current.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (PHOENIX-4332) Stats - Altering guidepost width on base table does not propagate to global index

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan reassigned PHOENIX-4332:
---

Assignee: Samarth Jain

> Stats - Altering guidepost width on base table does not propagate to global 
> index
> -
>
> Key: PHOENIX-4332
> URL: https://issues.apache.org/jira/browse/PHOENIX-4332
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.12.0
>    Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
>
> Altering guidepost with on data table does not propagate to global index 
> using {{ALTER TABLE}} command.
> Altering global index table runs in not allowed error.
> {noformat}
> ALTER TABLE IDX SET GUIDE_POSTS_WIDTH=1;
> Error: ERROR 1010 (42M01): Not allowed to mutate table. Cannot add/drop 
> column referenced by VIEW columnName=IDX (state=42M01,code=1010)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PHOENIX-4332) Stats - Altering guidepost width on base table does not propagate to global index

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4332:
---

 Summary: Stats - Altering guidepost width on base table does not 
propagate to global index
 Key: PHOENIX-4332
 URL: https://issues.apache.org/jira/browse/PHOENIX-4332
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.12.0
Reporter: Mujtaba Chohan


Altering guidepost with on data table does not propagate to global index using 
{{ALTER TABLE}} command.

Altering global index table runs in not allowed error.
{noformat}
ALTER TABLE IDX SET GUIDE_POSTS_WIDTH=1;
Error: ERROR 1010 (42M01): Not allowed to mutate table. Cannot add/drop column 
referenced by VIEW columnName=IDX (state=42M01,code=1010)
{noformat}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (PHOENIX-4287) Incorrect aggregate query results when stats are disable for parallelization

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16219532#comment-16219532
 ] 

Mujtaba Chohan edited comment on PHOENIX-4287 at 10/25/17 9:15 PM:
---

[~samarthjain] Just checked, this affects tables *without* any index as well as 
tables with global indexes.


was (Author: mujtabachohan):
[~samarthjain] Just checked, this affects tables with *without* any index as 
well as tables with global indexes.

> Incorrect aggregate query results when stats are disable for parallelization
> 
>
> Key: PHOENIX-4287
> URL: https://issues.apache.org/jira/browse/PHOENIX-4287
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.12.0
> Environment: HBase 1.3.1
>    Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
>  Labels: localIndex
> Fix For: 4.12.1
>
>
> With {{phoenix.use.stats.parallelization}} set to {{false}}, aggregate query 
> returns incorrect results when stats are available.
> With local index and stats disabled for parallelization:
> {noformat}
> explain select count(*) from TABLE_T;
> +---+-++---+
> | PLAN
>   | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO |
> +---+-++---+
> | CLIENT 0-CHUNK 332170 ROWS 625043899 BYTES PARALLEL 0-WAY RANGE SCAN OVER 
> TABLE_T [1]  | 625043899   | 332170 | 150792825 |
> | SERVER FILTER BY FIRST KEY ONLY 
>   | 625043899   | 332170 | 150792825 |
> | SERVER AGGREGATE INTO SINGLE ROW
>   | 625043899   | 332170 | 150792825 |
> +---+-++---+
> select count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 0 |
> +---+
> {noformat}
> Using data table
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-+++
> |   PLAN  
>  | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO_TS   |
> +--+-+++
> | CLIENT 2-CHUNK 332151 ROWS 438492470 BYTES PARALLEL 1-WAY FULL SCAN OVER 
> TABLE_T  | 438492470   | 332151 | 1507928257617  |
> | SERVER FILTER BY FIRST KEY ONLY 
>  | 438492470   | 332151 | 1507928257617  |
> | SERVER AGGREGATE INTO SINGLE ROW
>  | 438492470   | 332151 | 1507928257617  |
> +--+-+++
> select /*+NO_INDEX*/ count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 14|
> +---+
> {noformat}
> Without stats available, results are correct:
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-++--+
> | PLAN | 
> EST_BYTES_READ  | EST_ROWS_READ  | EST_INFO_TS  |
> +--+-++--+
> | CLIENT 2-CHUNK PARALLEL 1-WAY FULL SCAN OVER TABLE_T  | null| 
> null   | null |
> | SERVER FILTER BY FIRST KEY ONLY  | null 
>| null   | null |
> | SERVER AGGREGATE INTO SINGLE ROW | null 
>| null   | null |
> +

[jira] [Commented] (PHOENIX-4287) Incorrect aggregate query results when stats are disable for parallelization

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16219532#comment-16219532
 ] 

Mujtaba Chohan commented on PHOENIX-4287:
-

[~samarthjain] Just checked, this affects tables with *without* any index as 
well as tables with global indexes.

> Incorrect aggregate query results when stats are disable for parallelization
> 
>
> Key: PHOENIX-4287
> URL: https://issues.apache.org/jira/browse/PHOENIX-4287
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.12.0
> Environment: HBase 1.3.1
>    Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
>  Labels: localIndex
> Fix For: 4.12.1
>
>
> With {{phoenix.use.stats.parallelization}} set to {{false}}, aggregate query 
> returns incorrect results when stats are available.
> With local index and stats disabled for parallelization:
> {noformat}
> explain select count(*) from TABLE_T;
> +---+-++---+
> | PLAN
>   | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO |
> +---+-++---+
> | CLIENT 0-CHUNK 332170 ROWS 625043899 BYTES PARALLEL 0-WAY RANGE SCAN OVER 
> TABLE_T [1]  | 625043899   | 332170 | 150792825 |
> | SERVER FILTER BY FIRST KEY ONLY 
>   | 625043899   | 332170 | 150792825 |
> | SERVER AGGREGATE INTO SINGLE ROW
>   | 625043899   | 332170 | 150792825 |
> +---+-++---+
> select count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 0 |
> +---+
> {noformat}
> Using data table
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-+++
> |   PLAN  
>  | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO_TS   |
> +--+-+++
> | CLIENT 2-CHUNK 332151 ROWS 438492470 BYTES PARALLEL 1-WAY FULL SCAN OVER 
> TABLE_T  | 438492470   | 332151 | 1507928257617  |
> | SERVER FILTER BY FIRST KEY ONLY 
>  | 438492470   | 332151 | 1507928257617  |
> | SERVER AGGREGATE INTO SINGLE ROW
>  | 438492470   | 332151 | 1507928257617  |
> +--+-+++
> select /*+NO_INDEX*/ count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 14|
> +---+
> {noformat}
> Without stats available, results are correct:
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-++--+
> | PLAN | 
> EST_BYTES_READ  | EST_ROWS_READ  | EST_INFO_TS  |
> +--+-++--+
> | CLIENT 2-CHUNK PARALLEL 1-WAY FULL SCAN OVER TABLE_T  | null| 
> null   | null |
> | SERVER FILTER BY FIRST KEY ONLY  | null 
>| null   | null |
> | SERVER AGGREGATE INTO SINGLE ROW | null 
>| null   | null |
> +--+-++--+
> select /*+NO_INDEX*/ count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 27|
> +---+
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PHOENIX-4316) Local Index - Splitting a local index on multi-tenant view fails with TNF exception

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4316:
---

 Summary: Local Index - Splitting a local index on multi-tenant 
view fails with TNF exception
 Key: PHOENIX-4316
 URL: https://issues.apache.org/jira/browse/PHOENIX-4316
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.12.0
Reporter: Mujtaba Chohan


In the following logs TM is the base multi-tenant table and TV is the tenant 
specific view. Local index is created on tenant specific view. RS aborts when 
table is split.

{noformat}
2017-10-23 16:25:42,263 ERROR 
[localhost,34512,1508783072608-daughterOpener=420df77ad7317fcf213772974498e192] 
regionserver.HRegion: Could not initialize all stores for the 
region=TM,X\x001024163863277142772527737277482810122859132922143041163750200364,1508801142038.420df77ad7317fcf213772974498e192.
2017-10-23 16:25:42,275 INFO  
[localhost,34512,1508783072608-daughterOpener=420df77ad7317fcf213772974498e192] 
regionserver.HStore: Closed 0
2017-10-23 16:25:42,275 ERROR 
[localhost,34512,1508783072608-daughterOpener=c753e6d674dd5c797ea6cf23941ce9f3] 
regionserver.HRegion: Could not initialize all stores for the 
region=TM,,1508801142038.c753e6d674dd5c797ea6cf23941ce9f3.
2017-10-23 16:25:42,286 INFO  
[localhost,34512,1508783072608-daughterOpener=c753e6d674dd5c797ea6cf23941ce9f3] 
regionserver.HStore: Closed 0
2017-10-23 16:25:42,286 INFO  [RS:0;localhost:34512-splits-1508783666402] 
regionserver.SplitRequest: Running rollback/cleanup of failed split of 
TM,,1508799266515.f3c6ebcb4e605e0b5c2098633967d73e.; Failed 
localhost,34512,1508783072608-daughterOpener=c753e6d674dd5c797ea6cf23941ce9f3
java.io.IOException: Failed 
localhost,34512,1508783072608-daughterOpener=c753e6d674dd5c797ea6cf23941ce9f3
at 
org.apache.hadoop.hbase.regionserver.SplitTransactionImpl.openDaughters(SplitTransactionImpl.java:499)
at 
org.apache.hadoop.hbase.regionserver.SplitTransactionImpl.stepsAfterPONR(SplitTransactionImpl.java:597)
at 
org.apache.hadoop.hbase.regionserver.SplitTransactionImpl.execute(SplitTransactionImpl.java:580)
at 
org.apache.hadoop.hbase.regionserver.SplitRequest.doSplitting(SplitRequest.java:82)
at 
org.apache.hadoop.hbase.regionserver.SplitRequest.run(SplitRequest.java:154)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: java.io.IOException: java.io.IOException: 
org.apache.phoenix.schema.TableNotFoundException: ERROR 1012 (42M03): Table 
undefined. tableName=TV
at 
org.apache.hadoop.hbase.regionserver.HRegion.initializeStores(HRegion.java:952)
at 
org.apache.hadoop.hbase.regionserver.HRegion.initializeRegionInternals(HRegion.java:827)
at 
org.apache.hadoop.hbase.regionserver.HRegion.initialize(HRegion.java:802)
at 
org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:6708)
at 
org.apache.hadoop.hbase.regionserver.SplitTransactionImpl.openDaughterRegion(SplitTransactionImpl.java:731)
at 
org.apache.hadoop.hbase.regionserver.SplitTransactionImpl$DaughterOpener.run(SplitTransactionImpl.java:711)
... 1 more
Caused by: java.io.IOException: java.io.IOException: 
org.apache.phoenix.schema.TableNotFoundException: ERROR 1012 (42M03): Table 
undefined. tableName=TV
at 
org.apache.hadoop.hbase.regionserver.HStore.openStoreFiles(HStore.java:560)
at 
org.apache.hadoop.hbase.regionserver.HStore.loadStoreFiles(HStore.java:514)
at org.apache.hadoop.hbase.regionserver.HStore.(HStore.java:277)
at 
org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:5185)
at org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:926)
at org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:923)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
... 1 more
Caused by: java.io.IOException: 
org.apache.phoenix.schema.TableNotFoundException: ERROR 1012 (42M03): Table 
undefined. tableName=TV
at 
org.apache.hadoop.hbase.regionserver.IndexHalfStoreFileReaderGenerator.preStoreFileReaderOpen(IndexHalfStoreFileReaderGenerator.java:174)
at 
org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$64.call(RegionCoprocessorHost.java:1580)
at 
org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$RegionOperation.call(RegionCoprocessorHost.java:1673

[jira] [Created] (PHOENIX-4299) Local index - Data vs index row count does not match

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4299:
---

 Summary: Local index - Data vs index row count does not match
 Key: PHOENIX-4299
 URL: https://issues.apache.org/jira/browse/PHOENIX-4299
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.12.0
 Environment: HBase 1.3.1, Phoenix 4.12.0
Reporter: Mujtaba Chohan


* In my test row count of local index is ~3K less than the total row count of 
approx 5M when comparing it using {{count( *)}} aggregation with {{NO_INDEX}} 
hint. 
* For data shape, at-least 50% of the upserts leads to multiple version with 
batch size of 250 using 4 writer threads. There are no deletes.
* This mutable table contains 18 columns with 5 of them being keys
* There are a total of 5 covered local indexes on the table
* Table get automatically split in 8 regions

I'll update here with more info. about any split/compaction activity that 
happened around the timestamp for the missing rows.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PHOENIX-4291) Merge release script for mac and linux

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4291:

Attachment: PHOENIX-4291.patch

> Merge release script for mac and linux
> --
>
> Key: PHOENIX-4291
> URL: https://issues.apache.org/jira/browse/PHOENIX-4291
> Project: Phoenix
>  Issue Type: Improvement
>Affects Versions: 4.12.0
>        Reporter: Mujtaba Chohan
>    Assignee: Mujtaba Chohan
>Priority: Trivial
> Fix For: 4.12.1
>
> Attachments: PHOENIX-4291.patch
>
>
> Merging make_rc.sh and make_rc_on_mac.sh to make_rc_sh. This is based on 
> changes that [~jamestaylor] had in place to execute the script on a Mac.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PHOENIX-4291) Merge release script for mac and linux

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4291:
---

 Summary: Merge release script for mac and linux
 Key: PHOENIX-4291
 URL: https://issues.apache.org/jira/browse/PHOENIX-4291
 Project: Phoenix
  Issue Type: Improvement
Affects Versions: 4.12.0
Reporter: Mujtaba Chohan
Assignee: Mujtaba Chohan
Priority: Trivial
 Fix For: 4.12.1


Merging make_rc.sh and make_rc_on_mac.sh to make_rc_sh. This is based on 
changes that [~jamestaylor] had in place to execute the script on a Mac.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PHOENIX-4289) UPDATE STATISTICS command does not collect stats for local indexes

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4289:

Affects Version/s: 4.12.0

> UPDATE STATISTICS command does not collect stats for local indexes
> --
>
> Key: PHOENIX-4289
> URL: https://issues.apache.org/jira/browse/PHOENIX-4289
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.12.0
> Environment: HBase 1.3.1, Phoenix 4.12.0
>    Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
>
> With clean {{SYSTEM.STATS}} table and restarted HBase server+Phoenix client. 
> Ran {{UPDATE STATISTICS T ALL}} command. Global guidepost width is set to 
> 100M. No stats are generated for any of the local indexes on table T.
> {noformat}
> explain select count(*) from T;
> +---+-++--+
> |   PLAN| 
> EST_BYTES_READ  | EST_ROWS_READ  | EST_INFO_TS  |
> +---+-++--+
> | CLIENT 8-CHUNK PARALLEL 8-WAY RANGE SCAN OVER T [1]   | 
> null| null   | null |
> | SERVER FILTER BY FIRST KEY ONLY   | 
> null| null   | null |
> | SERVER AGGREGATE INTO SINGLE ROW  | 
> null| null   | null |
> +---+-++--+
> select * from system.stats;
> +--++-++--++
> |PHYSICAL_NAME | COLUMN_FAMILY  | GUIDE_POST_KEY  | 
> GUIDE_POSTS_WIDTH  |  LAST_STATS_UPDATE_TIME  | GUIDE_POSTS_ROW_COUNT  |
> +--++-++--++
> | T   || | null   | 
> 2017-10-16 18:36:57.884  | null   |
> | T   | 0  | [B@9bd0fa6  | 10099  |   
>| 75756  |
> | T   | 0  | [B@59d2103b | 10057  |   
>| 75748  |
> | T   | 0  | [B@39dcf4b0 | 10058  |   
>| 75748  |
> | T   | 0  | [B@6e4de19b | 10081  |   
>| 75743  |
> | T   | 0  | [B@f6c03cb  | 10044  |   
>| 75744  |
> | T   | 0  | [B@46f699d5 | 10023  |   
>| 75741  |
> | T   | 0  | [B@18518ccf | 10019  |   
>| 75749  |
> | T   | 0  | [B@1991f767 | 10097  |   
>| 75740  |
> | T   | 0  | [B@768ccdc5 | 10092  |   
>| 75740  |
> | T   | 0  | [B@4c6daf0  | 10026  |   
>| 75739  |
> | T   | 0  | [B@10650953 | 10054  |   
>| 75731  |
> | T   | 0  | [B@659eef7  | 10092  |   
>| 75741  |
> | T   | 0  | [B@162be91c | 10023  |   
>| 75752  |
> | T   | 0  | [B@2488b073 | 10096  |   
>| 75743  |
> | T   | 0  | [B@1c9f0a20 | 10025  |   
>| 75745  |
> | T   | 0  | [B@55787112 | 10104  |   
>| 75725  |
> | T   | 0  | [B@1cd201a8 | 10019  |   
>| 75748  |
> | T   | 0  | [B@7db82169 | 10080  |   
>| 75740  |
> | T   | 0  | [B@1992e

[jira] [Assigned] (PHOENIX-4289) UPDATE STATISTICS command does not collect stats for local indexes

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan reassigned PHOENIX-4289:
---

Assignee: Samarth Jain

> UPDATE STATISTICS command does not collect stats for local indexes
> --
>
> Key: PHOENIX-4289
> URL: https://issues.apache.org/jira/browse/PHOENIX-4289
> Project: Phoenix
>  Issue Type: Bug
> Environment: HBase 1.3.1, Phoenix 4.12.0
>        Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
>
> With clean {{SYSTEM.STATS}} table and restarted HBase server+Phoenix client. 
> Ran {{UPDATE STATISTICS T ALL}} command. Global guidepost width is set to 
> 100M. No stats are generated for any of the local indexes on table T.
> {noformat}
> explain select count(*) from T;
> +---+-++--+
> |   PLAN| 
> EST_BYTES_READ  | EST_ROWS_READ  | EST_INFO_TS  |
> +---+-++--+
> | CLIENT 8-CHUNK PARALLEL 8-WAY RANGE SCAN OVER T [1]   | 
> null| null   | null |
> | SERVER FILTER BY FIRST KEY ONLY   | 
> null| null   | null |
> | SERVER AGGREGATE INTO SINGLE ROW  | 
> null| null   | null |
> +---+-++--+
> select * from system.stats;
> +--++-++--++
> |PHYSICAL_NAME | COLUMN_FAMILY  | GUIDE_POST_KEY  | 
> GUIDE_POSTS_WIDTH  |  LAST_STATS_UPDATE_TIME  | GUIDE_POSTS_ROW_COUNT  |
> +--++-++--++
> | T   || | null   | 
> 2017-10-16 18:36:57.884  | null   |
> | T   | 0  | [B@9bd0fa6  | 10099  |   
>| 75756  |
> | T   | 0  | [B@59d2103b | 10057  |   
>| 75748  |
> | T   | 0  | [B@39dcf4b0 | 10058  |   
>| 75748  |
> | T   | 0  | [B@6e4de19b | 10081  |   
>| 75743  |
> | T   | 0  | [B@f6c03cb  | 10044  |   
>| 75744  |
> | T   | 0  | [B@46f699d5 | 10023  |   
>| 75741  |
> | T   | 0  | [B@18518ccf | 10019  |   
>| 75749  |
> | T   | 0  | [B@1991f767 | 10097  |   
>| 75740  |
> | T   | 0  | [B@768ccdc5 | 10092  |   
>| 75740  |
> | T   | 0  | [B@4c6daf0  | 10026  |   
>| 75739  |
> | T   | 0  | [B@10650953 | 10054  |   
>| 75731  |
> | T   | 0  | [B@659eef7  | 10092  |   
>| 75741  |
> | T   | 0  | [B@162be91c | 10023  |   
>| 75752  |
> | T   | 0  | [B@2488b073 | 10096  |   
>| 75743  |
> | T   | 0  | [B@1c9f0a20 | 10025  |   
>| 75745  |
> | T   | 0  | [B@55787112 | 10104  |   
>| 75725  |
> | T   | 0  | [B@1cd201a8 | 10019  |   
>| 75748  |
> | T   | 0  | [B@7db82169 | 10080  |   
>| 75740  |
> | T   | 0  | [B@1992eaf4 | 10079  | 

[jira] [Created] (PHOENIX-4289) UPDATE STATISTICS command does not collect stats for local indexes

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4289:
---

 Summary: UPDATE STATISTICS command does not collect stats for 
local indexes
 Key: PHOENIX-4289
 URL: https://issues.apache.org/jira/browse/PHOENIX-4289
 Project: Phoenix
  Issue Type: Bug
 Environment: HBase 1.3.1, Phoenix 4.12.0
Reporter: Mujtaba Chohan


With clean {{SYSTEM.STATS}} table and restarted HBase server+Phoenix client. 
Ran {{UPDATE STATISTICS T ALL}} command. Global guidepost width is set to 100M. 
No stats are generated for any of the local indexes on table T.

{noformat}
explain select count(*) from T;
+---+-++--+
|   PLAN| 
EST_BYTES_READ  | EST_ROWS_READ  | EST_INFO_TS  |
+---+-++--+
| CLIENT 8-CHUNK PARALLEL 8-WAY RANGE SCAN OVER T [1]   | 
null| null   | null |
| SERVER FILTER BY FIRST KEY ONLY   | 
null| null   | null |
| SERVER AGGREGATE INTO SINGLE ROW  | 
null| null   | null |
+---+-++--+

select * from system.stats;
+--++-++--++
|PHYSICAL_NAME | COLUMN_FAMILY  | GUIDE_POST_KEY  | 
GUIDE_POSTS_WIDTH  |  LAST_STATS_UPDATE_TIME  | GUIDE_POSTS_ROW_COUNT  |
+--++-++--++
| T   || | null   | 2017-10-16 
18:36:57.884  | null   |
| T   | 0  | [B@9bd0fa6  | 10099  | 
 | 75756  |
| T   | 0  | [B@59d2103b | 10057  | 
 | 75748  |
| T   | 0  | [B@39dcf4b0 | 10058  | 
 | 75748  |
| T   | 0  | [B@6e4de19b | 10081  | 
 | 75743  |
| T   | 0  | [B@f6c03cb  | 10044  | 
 | 75744  |
| T   | 0  | [B@46f699d5 | 10023  | 
 | 75741  |
| T   | 0  | [B@18518ccf | 10019  | 
 | 75749  |
| T   | 0  | [B@1991f767 | 10097  | 
 | 75740  |
| T   | 0  | [B@768ccdc5 | 10092  | 
 | 75740  |
| T   | 0  | [B@4c6daf0  | 10026  | 
 | 75739  |
| T   | 0  | [B@10650953 | 10054  | 
 | 75731  |
| T   | 0  | [B@659eef7  | 10092  | 
 | 75741  |
| T   | 0  | [B@162be91c | 10023  | 
 | 75752  |
| T   | 0  | [B@2488b073 | 10096  | 
 | 75743  |
| T   | 0  | [B@1c9f0a20 | 10025  | 
 | 75745  |
| T   | 0  | [B@55787112 | 10104  | 
 | 75725  |
| T   | 0  | [B@1cd201a8 | 10019  | 
 | 75748  |
| T   | 0  | [B@7db82169 | 10080  | 
 | 75740  |
| T   | 0  | [B@1992eaf4 | 10079  | 
 | 75733  |
| T   | 0  | [B@f74e835  | 10003  | 
 | 75746  |
| T   | 0  | [B@3276732  | 10118  | 
 | 75750  |
| T   | 0  | [B@3f28bd56 | 10019  | 
 | 75749  |
| T   | 0  | [B@31e3250d | 10091  | 
 | 75753  |
| T   | 0  | [B@19fe4644

[jira] [Commented] (PHOENIX-4287) Incorrect aggregate query results when stats are disable for parallelization

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204204#comment-16204204
 ] 

Mujtaba Chohan commented on PHOENIX-4287:
-

Results are incorrect for filter on leading/non-leading PK as well. Ex {{select 
/**+NO_INDEX**/ * from T where leadingKey='x'}}

> Incorrect aggregate query results when stats are disable for parallelization
> 
>
> Key: PHOENIX-4287
> URL: https://issues.apache.org/jira/browse/PHOENIX-4287
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.12.0
> Environment: HBase 1.3.1
>    Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
>
> With {{phoenix.use.stats.parallelization}} set to {{false}}, aggregate query 
> returns incorrect results when stats are available.
> With local index and stats disabled for parallelization:
> {noformat}
> explain select count(*) from TABLE_T;
> +---+-++---+
> | PLAN
>   | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO |
> +---+-++---+
> | CLIENT 0-CHUNK 332170 ROWS 625043899 BYTES PARALLEL 0-WAY RANGE SCAN OVER 
> TABLE_T [1]  | 625043899   | 332170 | 150792825 |
> | SERVER FILTER BY FIRST KEY ONLY 
>   | 625043899   | 332170 | 150792825 |
> | SERVER AGGREGATE INTO SINGLE ROW
>   | 625043899   | 332170 | 150792825 |
> +---+-++---+
> select count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 0 |
> +---+
> {noformat}
> Using data table
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-+++
> |   PLAN  
>  | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO_TS   |
> +--+-+++
> | CLIENT 2-CHUNK 332151 ROWS 438492470 BYTES PARALLEL 1-WAY FULL SCAN OVER 
> TABLE_T  | 438492470   | 332151 | 1507928257617  |
> | SERVER FILTER BY FIRST KEY ONLY 
>  | 438492470   | 332151 | 1507928257617  |
> | SERVER AGGREGATE INTO SINGLE ROW
>  | 438492470   | 332151 | 1507928257617  |
> +--+-+++
> select /*+NO_INDEX*/ count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 14|
> +---+
> {noformat}
> Without stats available, results are correct:
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-++--+
> | PLAN | 
> EST_BYTES_READ  | EST_ROWS_READ  | EST_INFO_TS  |
> +--+-++--+
> | CLIENT 2-CHUNK PARALLEL 1-WAY FULL SCAN OVER TABLE_T  | null| 
> null   | null |
> | SERVER FILTER BY FIRST KEY ONLY  | null 
>| null   | null |
> | SERVER AGGREGATE INTO SINGLE ROW | null 
>| null   | null |
> +--+-++--+
> select /*+NO_INDEX*/ count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 27|
> +---+
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (PHOENIX-4287) Incorrect aggregate query results when stats are disable for parallelization

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan reassigned PHOENIX-4287:
---

Assignee: Samarth Jain

> Incorrect aggregate query results when stats are disable for parallelization
> 
>
> Key: PHOENIX-4287
> URL: https://issues.apache.org/jira/browse/PHOENIX-4287
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.12.0
> Environment: HBase 1.3.1
>    Reporter: Mujtaba Chohan
>Assignee: Samarth Jain
>
> With {{phoenix.use.stats.parallelization}} set to {{false}}, aggregate query 
> returns incorrect results when stats are available.
> With local index and stats disabled for parallelization:
> {noformat}
> explain select count(*) from TABLE_T;
> +---+-++---+
> | PLAN
>   | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO |
> +---+-++---+
> | CLIENT 0-CHUNK 332170 ROWS 625043899 BYTES PARALLEL 0-WAY RANGE SCAN OVER 
> TABLE_T [1]  | 625043899   | 332170 | 150792825 |
> | SERVER FILTER BY FIRST KEY ONLY 
>   | 625043899   | 332170 | 150792825 |
> | SERVER AGGREGATE INTO SINGLE ROW
>   | 625043899   | 332170 | 150792825 |
> +---+-++---+
> select count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 0 |
> +---+
> {noformat}
> Using data table
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-+++
> |   PLAN  
>  | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO_TS   |
> +--+-+++
> | CLIENT 2-CHUNK 332151 ROWS 438492470 BYTES PARALLEL 1-WAY FULL SCAN OVER 
> TABLE_T  | 438492470   | 332151 | 1507928257617  |
> | SERVER FILTER BY FIRST KEY ONLY 
>  | 438492470   | 332151 | 1507928257617  |
> | SERVER AGGREGATE INTO SINGLE ROW
>  | 438492470   | 332151 | 1507928257617  |
> +--+-+++
> select /*+NO_INDEX*/ count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 14|
> +---+
> {noformat}
> Without stats available, results are correct:
> {noformat}
> explain select /*+NO_INDEX*/ count(*) from TABLE_T;
> +--+-++--+
> | PLAN | 
> EST_BYTES_READ  | EST_ROWS_READ  | EST_INFO_TS  |
> +--+-++--+
> | CLIENT 2-CHUNK PARALLEL 1-WAY FULL SCAN OVER TABLE_T  | null| 
> null   | null |
> | SERVER FILTER BY FIRST KEY ONLY  | null 
>| null   | null |
> | SERVER AGGREGATE INTO SINGLE ROW | null 
>| null   | null |
> +--+-++--+
> select /*+NO_INDEX*/ count(*) from TABLE_T;
> +---+
> | COUNT(1)  |
> +---+
> | 27|
> +---+
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PHOENIX-4287) Incorrect aggregate query results when stats are disable for parallelization

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4287:
---

 Summary: Incorrect aggregate query results when stats are disable 
for parallelization
 Key: PHOENIX-4287
 URL: https://issues.apache.org/jira/browse/PHOENIX-4287
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.12.0
 Environment: HBase 1.3.1
Reporter: Mujtaba Chohan


With {{phoenix.use.stats.parallelization}} set to {{false}}, aggregate query 
returns incorrect results when stats are available.

With local index and stats disabled for parallelization:
{noformat}
explain select count(*) from TABLE_T;
+---+-++---+
| PLAN  
| EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO |
+---+-++---+
| CLIENT 0-CHUNK 332170 ROWS 625043899 BYTES PARALLEL 0-WAY RANGE SCAN OVER 
TABLE_T [1]  | 625043899   | 332170 | 150792825 |
| SERVER FILTER BY FIRST KEY ONLY   
| 625043899   | 332170 | 150792825 |
| SERVER AGGREGATE INTO SINGLE ROW  
| 625043899   | 332170 | 150792825 |
+---+-++---+

select count(*) from TABLE_T;
+---+
| COUNT(1)  |
+---+
| 0 |
+---+
{noformat}

Using data table
{noformat}
explain select /*+NO_INDEX*/ count(*) from TABLE_T;
+--+-+++
|   PLAN
   | EST_BYTES_READ  | EST_ROWS_READ  |  EST_INFO_TS   |
+--+-+++
| CLIENT 2-CHUNK 332151 ROWS 438492470 BYTES PARALLEL 1-WAY FULL SCAN OVER 
TABLE_T  | 438492470   | 332151 | 1507928257617  |
| SERVER FILTER BY FIRST KEY ONLY   
   | 438492470   | 332151 | 1507928257617  |
| SERVER AGGREGATE INTO SINGLE ROW  
   | 438492470   | 332151 | 1507928257617  |
+--+-+++

select /*+NO_INDEX*/ count(*) from TABLE_T;
+---+
| COUNT(1)  |
+---+
| 14|
+---+
{noformat}

Without stats available, results are correct:
{noformat}
explain select /*+NO_INDEX*/ count(*) from TABLE_T;
+--+-++--+
| PLAN | 
EST_BYTES_READ  | EST_ROWS_READ  | EST_INFO_TS  |
+--+-++--+
| CLIENT 2-CHUNK PARALLEL 1-WAY FULL SCAN OVER TABLE_T  | null| 
null   | null |
| SERVER FILTER BY FIRST KEY ONLY  | null   
 | null   | null |
| SERVER AGGREGATE INTO SINGLE ROW | null   
 | null   | null |
+--+-++--+
select /*+NO_INDEX*/ count(*) from TABLE_T;
+---+
| COUNT(1)  |
+---+
| 27|
+---+
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [ANNOUNCE] New Phoenix committer: Vincent Poon

[Mujtaba Chohan]

Congrats Vincent!!

On Thu, Oct 12, 2017 at 10:03 AM, Josh Elser  wrote:

> Congrats Vincent!
>
>
> On 10/11/17 9:51 PM, James Taylor wrote:
>
>> On behalf of the Apache Phoenix PMC, I'm delighted to announce that
>> Vincent
>> Poon has accepted our invitation to become a committer. He's had a big
>> impact in helping to stabilize our secondary index implementation,
>> including the creation of an index scrutiny tool that will detect
>> out-of-sync issues [1].
>>
>> Looking forward to continued contributions.
>>
>> Please give Vincent a warm welcome to the project!
>>
>>  James
>>
>>
>> [1] https://phoenix.apache.org/secondary_indexing.html#Index_Scr
>> utiny_Tool
>>
>>

Re: [ANNOUNCE] New Phoenix committer: Ethan Wang

[Mujtaba Chohan]

Congrats Ethan!!

On Thu, Oct 12, 2017 at 10:03 AM, Josh Elser  wrote:

> Congrats Ethan!
>
>
> On 10/11/17 9:45 PM, James Taylor wrote:
>
>> On behalf of the Apache Phoenix PMC, I'm please to announce that Ethan
>> Wang
>> has accepted our invitation to become a committer. He's behind some of the
>> great new 4.12 features of table sampling [1] and approximate count
>> distinct [2] along with contributing to the less sexy work of helping to
>> stabilize our unit tests.
>>
>> Please give Ethan a warm welcome to the project!
>>
>>  James
>>
>> [1] https://phoenix.apache.org/tablesample.html
>> [2] https://phoenix.apache.org/language/functions.html#approx_
>> count_distinct
>>
>>

[jira] [Resolved] (PHOENIX-4194) Modify RoundFloorCeilFuncIT, RowValueConstructorIT, SaltedTableIT, TenantIdTypeIT, StoreNullsIT and RebuildIndexConnectionPropsIT to not use CurrentSCN

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan resolved PHOENIX-4194.
-
Resolution: Fixed

> Modify RoundFloorCeilFuncIT, RowValueConstructorIT, SaltedTableIT, 
> TenantIdTypeIT, StoreNullsIT and RebuildIndexConnectionPropsIT to not use 
> CurrentSCN
> ---
>
> Key: PHOENIX-4194
> URL: https://issues.apache.org/jira/browse/PHOENIX-4194
> Project: Phoenix
>  Issue Type: Test
>    Reporter: Mujtaba Chohan
>    Assignee: Mujtaba Chohan
> Fix For: 4.12.0
>
> Attachments: PHOENIX-4194.patch, PHOENIX-4194_v2.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (PHOENIX-4213) Modify ExtendedQueryExecIT and FunkyNamesIT to not use currentSCN

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan resolved PHOENIX-4213.
-
Resolution: Fixed

> Modify ExtendedQueryExecIT and FunkyNamesIT to not use currentSCN
> -
>
> Key: PHOENIX-4213
> URL: https://issues.apache.org/jira/browse/PHOENIX-4213
> Project: Phoenix
>  Issue Type: Test
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
> Fix For: 4.12.0
>
> Attachments: PHOENIX-4213.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (PHOENIX-4204) Modify SequenceBulkAllocationIT.java to not use currentSCN

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan resolved PHOENIX-4204.
-
Resolution: Fixed

> Modify SequenceBulkAllocationIT.java to not use currentSCN
> --
>
> Key: PHOENIX-4204
> URL: https://issues.apache.org/jira/browse/PHOENIX-4204
> Project: Phoenix
>  Issue Type: Test
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
> Attachments: PHOENIX-4204.patch, PHOENIX-4204_v2.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (PHOENIX-4204) Modify SequenceBulkAllocationIT.java to not use currentSCN

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168592#comment-16168592
 ] 

Mujtaba Chohan commented on PHOENIX-4204:
-

Thanks [~jamestaylor]. Committed (with removed limit 1)

> Modify SequenceBulkAllocationIT.java to not use currentSCN
> --
>
> Key: PHOENIX-4204
> URL: https://issues.apache.org/jira/browse/PHOENIX-4204
> Project: Phoenix
>  Issue Type: Test
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
> Attachments: PHOENIX-4204.patch, PHOENIX-4204_v2.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (PHOENIX-4199) Modify SequenceIT.java to not use CurrentSCN

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan resolved PHOENIX-4199.
-
Resolution: Fixed

Thanks [~jamestaylor]. Committed.

> Modify SequenceIT.java to not use CurrentSCN
> 
>
> Key: PHOENIX-4199
> URL: https://issues.apache.org/jira/browse/PHOENIX-4199
> Project: Phoenix
>  Issue Type: Test
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
> Attachments: PHOENIX-4199.patch, PHOENIX-4199_v2.patch, 
> PHOENIX-4199_v3.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (PHOENIX-4199) Modify SequenceIT.java to not use CurrentSCN

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167133#comment-16167133
 ] 

Mujtaba Chohan edited comment on PHOENIX-4199 at 9/15/17 12:09 AM:
---

Need your insight here [~jamestaylor]. Now down to last 5 out of 55 tests which 
are failing on assertions when {{FROM SYSTEM.SEQUENCE}} is removed from 
{{SELECT NEXT VALUE FOR %s FROM SYSTEM.SEQUENCE}} in PHOENIX-4199_v2.patch


was (Author: mujtabachohan):
Need your insight here [~jamestaylor]. Now down to last 5 out of 55 tests which 
are failing on assertions when {{FROM SYSTEM.SEQUENCE}} is removed from 
{{SELECT NEXT VALUE FOR %s FROM SYSTEM.CATALOG}} in PHOENIX-4199_v2.patch

> Modify SequenceIT.java to not use CurrentSCN
> 
>
> Key: PHOENIX-4199
> URL: https://issues.apache.org/jira/browse/PHOENIX-4199
> Project: Phoenix
>  Issue Type: Test
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
> Attachments: PHOENIX-4199.patch, PHOENIX-4199_v2.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PHOENIX-4199) Modify SequenceIT.java to not use CurrentSCN

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4199:

Attachment: PHOENIX-4199_v2.patch

Need your insight here [~jamestaylor]. Now down to last 5 out of 55 tests which 
are failing on assertions when {{FROM SYSTEM.SEQUENCE}} is removed from 
{{SELECT NEXT VALUE FOR %s FROM SYSTEM.CATALOG}} in PHOENIX-4199_v2.patch

> Modify SequenceIT.java to not use CurrentSCN
> 
>
> Key: PHOENIX-4199
> URL: https://issues.apache.org/jira/browse/PHOENIX-4199
> Project: Phoenix
>  Issue Type: Test
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
> Attachments: PHOENIX-4199.patch, PHOENIX-4199_v2.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PHOENIX-4204) Modify SequenceBulkAllocationIT.java to not use currentSCN

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4204:

Attachment: PHOENIX-4204_v2.patch

[~jamestaylor] PHOENIX-4204_v2.patch will all passing tests.

> Modify SequenceBulkAllocationIT.java to not use currentSCN
> --
>
> Key: PHOENIX-4204
> URL: https://issues.apache.org/jira/browse/PHOENIX-4204
> Project: Phoenix
>  Issue Type: Test
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
> Attachments: PHOENIX-4204.patch, PHOENIX-4204_v2.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PHOENIX-4213) Modify ExtendedQueryExecIT and FunkyNamesIT to not use currentSCN

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4213:

Attachment: PHOENIX-4213.patch

> Modify ExtendedQueryExecIT and FunkyNamesIT to not use currentSCN
> -
>
> Key: PHOENIX-4213
> URL: https://issues.apache.org/jira/browse/PHOENIX-4213
> Project: Phoenix
>  Issue Type: Test
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
> Fix For: 4.12.0
>
> Attachments: PHOENIX-4213.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PHOENIX-4213) Modify ExtendedQueryExecIT and FunkyNamesIT to not use currentSCN

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4213:
---

 Summary: Modify ExtendedQueryExecIT and FunkyNamesIT to not use 
currentSCN
 Key: PHOENIX-4213
 URL: https://issues.apache.org/jira/browse/PHOENIX-4213
 Project: Phoenix
  Issue Type: Test
Reporter: Mujtaba Chohan
Assignee: Mujtaba Chohan
 Fix For: 4.12.0






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (PHOENIX-4197) Issue with creating multiple sequences

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan resolved PHOENIX-4197.
-
Resolution: Not A Problem

This works with your change [~jamestaylor]. After this, now uncovering that 
there are a couple of other tweaks needed in SequenceIT and 
SequenceBulkAllocationIT tests for which I'll work on updating those patches.

> Issue with creating multiple sequences
> --
>
> Key: PHOENIX-4197
> URL: https://issues.apache.org/jira/browse/PHOENIX-4197
> Project: Phoenix
>  Issue Type: Bug
>    Reporter: Mujtaba Chohan
> Attachments: SeqIT.java
>
>
> [~jamestaylor] Please see the attached test. If I drop any prior sequences 
> then the test passes fine i.e. un-comment 
> {{conn.createStatement().execute("DROP SEQUENCE BEFORE_TEST");}} then this 
> test passes otherwise it fails with:
> {noformat}
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertFalse(Assert.java:64)
>   at org.junit.Assert.assertFalse(Assert.java:74)
>   at 
> org.apache.phoenix.end2end.SequenceIT.assertSequenceValuesForSingleRow(SequenceIT.java:88)
>   at 
> org.apache.phoenix.end2end.SequenceIT.testSequenceDefault(SequenceIT.java:73)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (PHOENIX-4197) Issue with creating multiple sequences

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16165459#comment-16165459
 ] 

Mujtaba Chohan commented on PHOENIX-4197:
-

Thanks [~jamestaylor] I'll try this.

> Issue with creating multiple sequences
> --
>
> Key: PHOENIX-4197
> URL: https://issues.apache.org/jira/browse/PHOENIX-4197
> Project: Phoenix
>  Issue Type: Bug
>    Reporter: Mujtaba Chohan
> Attachments: SeqIT.java
>
>
> [~jamestaylor] Please see the attached test. If I drop any prior sequences 
> then the test passes fine i.e. un-comment 
> {{conn.createStatement().execute("DROP SEQUENCE BEFORE_TEST");}} then this 
> test passes otherwise it fails with:
> {noformat}
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertFalse(Assert.java:64)
>   at org.junit.Assert.assertFalse(Assert.java:74)
>   at 
> org.apache.phoenix.end2end.SequenceIT.assertSequenceValuesForSingleRow(SequenceIT.java:88)
>   at 
> org.apache.phoenix.end2end.SequenceIT.testSequenceDefault(SequenceIT.java:73)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PHOENIX-4204) Modify SequenceBulkAllocationIT.java to not use currentSCN

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4204:

Attachment: PHOENIX-4204.patch

> Modify SequenceBulkAllocationIT.java to not use currentSCN
> --
>
> Key: PHOENIX-4204
> URL: https://issues.apache.org/jira/browse/PHOENIX-4204
> Project: Phoenix
>  Issue Type: Test
>    Reporter: Mujtaba Chohan
> Attachments: PHOENIX-4204.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (PHOENIX-4204) Modify SequenceBulkAllocationIT.java to not use currentSCN

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan reassigned PHOENIX-4204:
---

Assignee: Mujtaba Chohan

> Modify SequenceBulkAllocationIT.java to not use currentSCN
> --
>
> Key: PHOENIX-4204
> URL: https://issues.apache.org/jira/browse/PHOENIX-4204
> Project: Phoenix
>  Issue Type: Test
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
> Attachments: PHOENIX-4204.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PHOENIX-4204) Modify SequenceBulkAllocationIT.java to not use currentSCN

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4204:
---

 Summary: Modify SequenceBulkAllocationIT.java to not use currentSCN
 Key: PHOENIX-4204
 URL: https://issues.apache.org/jira/browse/PHOENIX-4204
 Project: Phoenix
  Issue Type: Test
Reporter: Mujtaba Chohan






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PHOENIX-4199) Modify SequenceIT.java to not use CurrentSCN

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4199:

Attachment: PHOENIX-4199.patch

> Modify SequenceIT.java to not use CurrentSCN
> 
>
> Key: PHOENIX-4199
> URL: https://issues.apache.org/jira/browse/PHOENIX-4199
> Project: Phoenix
>  Issue Type: Test
>    Reporter: Mujtaba Chohan
> Attachments: PHOENIX-4199.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (PHOENIX-4199) Modify SequenceIT.java to not use CurrentSCN

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan reassigned PHOENIX-4199:
---

Assignee: Mujtaba Chohan

> Modify SequenceIT.java to not use CurrentSCN
> 
>
> Key: PHOENIX-4199
> URL: https://issues.apache.org/jira/browse/PHOENIX-4199
> Project: Phoenix
>  Issue Type: Test
>    Reporter: Mujtaba Chohan
>        Assignee: Mujtaba Chohan
> Attachments: PHOENIX-4199.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PHOENIX-4199) Modify SequenceIT.java to not use CurrentSCN

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4199:
---

 Summary: Modify SequenceIT.java to not use CurrentSCN
 Key: PHOENIX-4199
 URL: https://issues.apache.org/jira/browse/PHOENIX-4199
 Project: Phoenix
  Issue Type: Test
Reporter: Mujtaba Chohan






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (PHOENIX-4188) Disable DTD parsing on Pherf XML documents

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16163316#comment-16163316
 ] 

Mujtaba Chohan commented on PHOENIX-4188:
-

+1. Thanks [~elserj]

> Disable DTD parsing on Pherf XML documents
> --
>
> Key: PHOENIX-4188
> URL: https://issues.apache.org/jira/browse/PHOENIX-4188
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Josh Elser
>Assignee: Josh Elser
> Fix For: 4.12.0
>
> Attachments: PHOENIX-4188.001.patch, PHOENIX-4188.002.patch
>
>
> A security scan dinged Phoenix for an external entities attack on the XML 
> files that Pherf creates.
> We can easily work around it by disabling the inline doctype definition in 
> the XML parser we use.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (PHOENIX-4197) Issue with creating multiple sequences

[Mujtaba Chohan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mujtaba Chohan updated PHOENIX-4197:

Attachment: SeqIT.java

> Issue with creating multiple sequences
> --
>
> Key: PHOENIX-4197
> URL: https://issues.apache.org/jira/browse/PHOENIX-4197
> Project: Phoenix
>  Issue Type: Bug
>    Reporter: Mujtaba Chohan
> Attachments: SeqIT.java
>
>
> [~jamestaylor] Please see the attached test. If I drop any prior sequences 
> then the test passes fine i.e. un-comment 
> {{conn.createStatement().execute("DROP SEQUENCE BEFORE_TEST");}} then this 
> test passes otherwise it fails with:
> {noformat}
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertFalse(Assert.java:64)
>   at org.junit.Assert.assertFalse(Assert.java:74)
>   at 
> org.apache.phoenix.end2end.SequenceIT.assertSequenceValuesForSingleRow(SequenceIT.java:88)
>   at 
> org.apache.phoenix.end2end.SequenceIT.testSequenceDefault(SequenceIT.java:73)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (PHOENIX-4197) Issue with creating multiple sequences

[Mujtaba Chohan (JIRA)]

Mujtaba Chohan created PHOENIX-4197:
---

 Summary: Issue with creating multiple sequences
 Key: PHOENIX-4197
 URL: https://issues.apache.org/jira/browse/PHOENIX-4197
 Project: Phoenix
  Issue Type: Bug
Reporter: Mujtaba Chohan


[~jamestaylor] Please see the attached test. If I drop any prior sequences then 
the test passes fine i.e. un-comment {{conn.createStatement().execute("DROP 
SEQUENCE BEFORE_TEST");}} then this test passes otherwise it fails with:

{noformat}
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertFalse(Assert.java:64)
at org.junit.Assert.assertFalse(Assert.java:74)
at 
org.apache.phoenix.end2end.SequenceIT.assertSequenceValuesForSingleRow(SequenceIT.java:88)
at 
org.apache.phoenix.end2end.SequenceIT.testSequenceDefault(SequenceIT.java:73)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (PHOENIX-4193) Pherf - llegalArgumentException while DataTypeMapping some standard field e.g. SMALLINIT, TINYINT, BOOLEAN

[Mujtaba Chohan (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16162236#comment-16162236
 ] 

Mujtaba Chohan commented on PHOENIX-4193:
-

[~rgore] You need to use supported datatypes for now. Meanwhile as I add 
support for the datatypes you need, as a  workaround you can use similar 
datatypes. Ex. {{INT}} in place of {{TIMYINT}}

> Pherf - llegalArgumentException while DataTypeMapping some standard field 
> e.g. SMALLINIT, TINYINT, BOOLEAN
> --
>
> Key: PHOENIX-4193
> URL: https://issues.apache.org/jira/browse/PHOENIX-4193
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Ravindra Gore
>
> Currently only standard types are supported in Pherf scenarios generation. 
> To generate the scenarios for tables with non-supported data types, we try 
> mapping them to supported type.
> e.g. INTEGER to TINYINT mapping 
> 
>  INTEGER
>  RANDOM
>  2
>  0
>  10
>  APP_ID
> 
> Though generation of the test data fails with the gack:
> java.lang.IllegalArgumentException: No enum constant 
> org.apache.phoenix.pherf.configuration.DataTypeMapping.TINYINT
> java.lang.IllegalArgumentException: No enum constant 
> org.apache.phoenix.pherf.configuration.DataTypeMapping.TINYINT
>   at java.lang.Enum.valueOf(Enum.java:238)
>   at 
> org.apache.phoenix.pherf.configuration.DataTypeMapping.valueOf(DataTypeMapping.java:23)
>   at 
> org.apache.phoenix.pherf.util.PhoenixUtil.getColumnsFromPhoenix(PhoenixUtil.java:248)
>   at 
> org.apache.phoenix.pherf.workload.WriteWorkload.getBatches(WriteWorkload.java:208)
>   at 
> org.apache.phoenix.pherf.workload.WriteWorkload.exec(WriteWorkload.java:182)
>   at 
> org.apache.phoenix.pherf.workload.WriteWorkload.access$100(WriteWorkload.java:56)
>   at 
> org.apache.phoenix.pherf.workload.WriteWorkload$1.run(WriteWorkload.java:159)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Same issue is observerd for BOOLEAN and SMALLINT.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)