[GitHub] phoenix issue #159: PHOENIX-2535 Create shaded clients (thin + thick)

Github user ss77892 commented on the issue: https://github.com/apache/phoenix/pull/159 Updated version for better review --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled

[jira] [Commented] (PHOENIX-2535) Create shaded clients (thin + thick)

[ https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311797#comment-15311797 ] ASF GitHub Bot commented on PHOENIX-2535: - Github user ss77892 commented on the issue:

[jira] [Commented] (PHOENIX-2535) Create shaded clients (thin + thick)

[ https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311784#comment-15311784 ] Sergey Soldatov commented on PHOENIX-2535: -- This target is collecting all dependency jars into

[jira] [Updated] (PHOENIX-2535) Create shaded clients (thin + thick)

[ https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Soldatov updated PHOENIX-2535: - Attachment: PHOENIX-2535-7.patch removed artifact jars from phoenix-server,

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311600#comment-15311600 ] James Taylor commented on PHOENIX-258: -- +1. Awesome job, [~lhofhansl]. I love the trick you thought

[jira] [Commented] (PHOENIX-2956) apache-rat plugin error: Too many unapproved licenses

[ https://issues.apache.org/jira/browse/PHOENIX-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311552#comment-15311552 ] ASF GitHub Bot commented on PHOENIX-2956: - Github user shijinkui commented on the issue:

[GitHub] phoenix issue #172: [PHOENIX-2956] apache-rat plugin error: Too many unappro...

Github user shijinkui commented on the issue: https://github.com/apache/phoenix/pull/172 cc @bridiver @joshelser --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311543#comment-15311543 ] Lars Hofhansl commented on PHOENIX-258: --- bq. I think what we need is an int[] indexed by the slot

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311539#comment-15311539 ] Lars Hofhansl commented on PHOENIX-258: --- BTW... Here's the HBase logic in FilterList to AND filters

[jira] [Commented] (PHOENIX-2535) Create shaded clients (thin + thick)

[ https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311481#comment-15311481 ] Sergey Soldatov commented on PHOENIX-2535: -- [~mujtabachohan], [~enis] I will remove the unused

[jira] [Updated] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-258: -- Attachment: 258-v16.txt -v16 fixes the cornercase - and makes it simpler! > Use skip scan

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311408#comment-15311408 ] Lars Hofhansl commented on PHOENIX-258: --- Actually, so here's a case that does not work: 1,

[jira] [Commented] (PHOENIX-2942) Incorrect results for order by queries

[ https://issues.apache.org/jira/browse/PHOENIX-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311394#comment-15311394 ] Mujtaba Chohan commented on PHOENIX-2942: - FYI wrong order is also returned for {{integer}} and

[jira] [Updated] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-258: -- Attachment: (was: 258-v15.txt) > Use skip scan when SELECT DISTINCT on leading row key

[jira] [Updated] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-258: -- Attachment: 258-v15.txt just fixes a spelling mistake in the comments > Use skip scan when

[jira] [Updated] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-258: -- Attachment: 258-v15.txt -v15 removes the VARBINARY logic from DistinctPrefixFilter. Should be

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311293#comment-15311293 ] Lars Hofhansl commented on PHOENIX-258: --- bq. For example, if we have a schema like VARCHAR, INT,

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311262#comment-15311262 ] Lars Hofhansl commented on PHOENIX-258: --- bq. What if you have these three rows (assume INT, 2 byte

[jira] [Commented] (PHOENIX-2931) Phoenix client asks users to provide configs in cli that are present on the machine in hbase conf

[ https://issues.apache.org/jira/browse/PHOENIX-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311232#comment-15311232 ] Alicia Ying Shu commented on PHOENIX-2931: -- I have revised the patch to get defaults from

[jira] [Commented] (PHOENIX-2919) PreparedStatement Returns Incorrect Number of Deleted Records

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

[jira] [Closed] (PHOENIX-2895) Add bind parameter support for WhereOptimizer

[ https://issues.apache.org/jira/browse/PHOENIX-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue closed PHOENIX-2895. > Add bind parameter support for WhereOptimizer > - > >

[jira] [Resolved] (PHOENIX-2895) Add bind parameter support for WhereOptimizer

[ https://issues.apache.org/jira/browse/PHOENIX-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue resolved PHOENIX-2895. -- Resolution: Duplicate > Add bind parameter support for WhereOptimizer >

[jira] [Updated] (PHOENIX-2954) Avoid doing a full sort if the input is ordered on the leading edge of the sort key

[ https://issues.apache.org/jira/browse/PHOENIX-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated PHOENIX-2954: - Issue Type: Improvement (was: Bug) > Avoid doing a full sort if the input is ordered on the

[jira] [Updated] (PHOENIX-2957) WhereOptimizer to provide an estimate of key selectivity for key filters containing bind variables

[ https://issues.apache.org/jira/browse/PHOENIX-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated PHOENIX-2957: - Issue Type: New Feature (was: Bug) > WhereOptimizer to provide an estimate of key selectivity

[jira] [Updated] (PHOENIX-2903) Handle split during scan for row key ordered aggregations

[ https://issues.apache.org/jira/browse/PHOENIX-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2903: -- Attachment: PHOENIX-2903_v4_wip.patch WIP patch > Handle split during scan for row key

[jira] [Commented] (PHOENIX-2940) Remove STATS RPCs from rowlock

[ https://issues.apache.org/jira/browse/PHOENIX-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310981#comment-15310981 ] James Taylor commented on PHOENIX-2940: --- [~ndimiduk] - we don't use stats on the server-side, only

[jira] [Updated] (PHOENIX-2942) Incorrect results for order by queries

[ https://issues.apache.org/jira/browse/PHOENIX-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mujtaba Chohan updated PHOENIX-2942: Attachment: PHOENIX-2942-utest.patch utest attached. > Incorrect results for order by

Re: Are we ready for 4.8.0 RC?

On Wed, Jun 1, 2016 at 10:58 AM, Josh Elser wrote: > I can try to help knock out some of those issues you mentioned as well, > Nick. You mean my metacache woes? That's more than I'd hoped for! https://issues.apache.org/jira/browse/PHOENIX-2941

[jira] [Resolved] (PHOENIX-2919) PreparedStatement Returns Incorrect Number of Deleted Records

[ https://issues.apache.org/jira/browse/PHOENIX-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain resolved PHOENIX-2919. --- Resolution: Fixed > PreparedStatement Returns Incorrect Number of Deleted Records >

[jira] [Commented] (PHOENIX-2962) Compilation issue on 4.x-HBase-1.1

[ https://issues.apache.org/jira/browse/PHOENIX-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310910#comment-15310910 ] Josh Elser commented on PHOENIX-2962: - bq. the branch was getting compiled locally without any

[jira] [Commented] (PHOENIX-2535) Create shaded clients (thin + thick)

[ https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310908#comment-15310908 ] Enis Soztutar commented on PHOENIX-2535: [~sergey.soldatov] did you see my comment here:

[jira] [Commented] (PHOENIX-2961) select on a composite primary key fails when DESC is set in the table

[ https://issues.apache.org/jira/browse/PHOENIX-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310905#comment-15310905 ] James Taylor commented on PHOENIX-2961: --- My first guess is that the full row key(s) we produce for

[jira] [Updated] (PHOENIX-2961) select on a composite primary key fails when DESC is set in the table

[ https://issues.apache.org/jira/browse/PHOENIX-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2961: -- Labels: SFDC (was: ) > select on a composite primary key fails when DESC is set in the table

[jira] [Updated] (PHOENIX-2961) select on a composite primary key fails when DESC is set in the table

[ https://issues.apache.org/jira/browse/PHOENIX-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2961: -- Assignee: Samarth Jain > select on a composite primary key fails when DESC is set in the

[jira] [Updated] (PHOENIX-2961) select on a composite primary key fails when DESC is set in the table

[ https://issues.apache.org/jira/browse/PHOENIX-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2961: -- Fix Version/s: 4.8.0 > select on a composite primary key fails when DESC is set in the table

[jira] [Commented] (PHOENIX-2962) Compilation issue on 4.x-HBase-1.1

[ https://issues.apache.org/jira/browse/PHOENIX-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310899#comment-15310899 ] Ankit Singhal commented on PHOENIX-2962: [~elserj] , Not sure why the build was failing on

[jira] [Commented] (PHOENIX-2955) replace xpath to xmllint at make_rc.sh

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

[jira] [Resolved] (PHOENIX-2962) Compilation issue on 4.x-HBase-1.1

[ https://issues.apache.org/jira/browse/PHOENIX-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved PHOENIX-2962. - Resolution: Fixed > Compilation issue on 4.x-HBase-1.1 > -- > >

[jira] [Commented] (PHOENIX-2962) Compilation issue on 4.x-HBase-1.1

[ https://issues.apache.org/jira/browse/PHOENIX-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310791#comment-15310791 ] Josh Elser commented on PHOENIX-2962: - Careful on those backports, [~ankit.singhal]. Looks like your

[jira] [Created] (PHOENIX-2962) Compilation issue on 4.x-HBase-1.1

Josh Elser created PHOENIX-2962: --- Summary: Compilation issue on 4.x-HBase-1.1 Key: PHOENIX-2962 URL: https://issues.apache.org/jira/browse/PHOENIX-2962 Project: Phoenix Issue Type: Bug

Re: Are we ready for 4.8.0 RC?

+1 VOTE is ongoing over on dev@calcite.a.o for an Avatica 1.8.0 (anyone with a binding vote over there would be appreciated too) This would be a nice gain for Phoenix-4.8 (perf improvements, new features, better docs, etc). I can try to help knock out some of those issues you mentioned as

[jira] [Resolved] (PHOENIX-2955) replace xpath to xmllint at make_rc.sh

[ https://issues.apache.org/jira/browse/PHOENIX-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved PHOENIX-2955. - Resolution: Fixed Thanks again for your contribution, [~shijinkui]! > replace xpath to xmllint

[jira] [Updated] (PHOENIX-2955) replace xpath to xmllint at make_rc.sh

[ https://issues.apache.org/jira/browse/PHOENIX-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-2955: Fix Version/s: 4.8.0 > replace xpath to xmllint at make_rc.sh >

[jira] [Updated] (PHOENIX-2955) replace xpath to xmllint at make_rc.sh

[ https://issues.apache.org/jira/browse/PHOENIX-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-2955: Assignee: shijinkui > replace xpath to xmllint at make_rc.sh >

[jira] [Commented] (PHOENIX-2955) replace xpath to xmllint at make_rc.sh

[ https://issues.apache.org/jira/browse/PHOENIX-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310740#comment-15310740 ] ASF GitHub Bot commented on PHOENIX-2955: - Github user asfgit closed the pull request at:

[GitHub] phoenix pull request #170: [PHOENIX-2955] use xmllint for parsing phoenix na...

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

[jira] [Commented] (PHOENIX-2955) replace xpath to xmllint at make_rc.sh

[ https://issues.apache.org/jira/browse/PHOENIX-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310738#comment-15310738 ] Josh Elser commented on PHOENIX-2955: - bq. This looks fine to me – I'll merge it in. Actually, I'm

[jira] [Updated] (PHOENIX-2961) select on a composite primary key fails when DESC is set in the table

[ https://issues.apache.org/jira/browse/PHOENIX-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhiraj Hegde updated PHOENIX-2961: -- Attachment: test1.sql Attaching the sql statements in a file (same as above description) >

[jira] [Commented] (PHOENIX-2955) replace xpath to xmllint at make_rc.sh

[ https://issues.apache.org/jira/browse/PHOENIX-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310729#comment-15310729 ] Josh Elser commented on PHOENIX-2955: - Thanks for the pull request, [~shijinkui]! This looks fine to

[jira] [Created] (PHOENIX-2961) select on a composite primary key fails when DESC is set in the table

Dhiraj Hegde created PHOENIX-2961: - Summary: select on a composite primary key fails when DESC is set in the table Key: PHOENIX-2961 URL: https://issues.apache.org/jira/browse/PHOENIX-2961 Project:

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310723#comment-15310723 ] James Taylor commented on PHOENIX-258: -- I think what we need is an int[] indexed by the slot

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310668#comment-15310668 ] James Taylor commented on PHOENIX-258: -- What if you have these three rows (assume INT, 2 byte

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310651#comment-15310651 ] Lars Hofhansl commented on PHOENIX-258: --- bq. The reverse scan case is tricky. Padding with a single

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310630#comment-15310630 ] Lars Hofhansl commented on PHOENIX-258: --- "cannot" should "can only"! > Use skip scan when SELECT

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310640#comment-15310640 ] James Taylor commented on PHOENIX-258: -- (and yes, you're correct - don't need to worry about

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310636#comment-15310636 ] James Taylor commented on PHOENIX-258: -- Yes, good point, [~lhofhansl]. The reverse scan case is

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310627#comment-15310627 ] Lars Hofhansl commented on PHOENIX-258: --- So specifically: bq. You have to pad with some number of

[jira] [Updated] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-258: -- Attachment: 258-v14.txt Pretty happy with -v14 Just need to know about the VARBINARY issue,

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310571#comment-15310571 ] Lars Hofhansl commented on PHOENIX-258: --- [~giacomotaylor], VARBINARY can only be last in a PK,

[jira] [Commented] (PHOENIX-2946) Comparison between date and timestamp always returns true

[ https://issues.apache.org/jira/browse/PHOENIX-2946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310539#comment-15310539 ] Kevin Liew commented on PHOENIX-2946: - I forgot to do {code} select * from test {code} but it shows

[jira] [Commented] (PHOENIX-2596) Asynchronous Local Index is not available

[ https://issues.apache.org/jira/browse/PHOENIX-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310506#comment-15310506 ] Hadoop QA commented on PHOENIX-2596: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (PHOENIX-2959) Ignore serial hint for queries doing an ORDER BY not along the PK axis

[ https://issues.apache.org/jira/browse/PHOENIX-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310474#comment-15310474 ] Ankit Singhal commented on PHOENIX-2959: In case of AggregatePlan, I think, we should be

[jira] [Commented] (PHOENIX-2209) Building Local Index Asynchronously via IndexTool fails to populate index table

[ https://issues.apache.org/jira/browse/PHOENIX-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310378#comment-15310378 ] Rajeshbabu Chintaguntla commented on PHOENIX-2209: -- [~jamestaylor] This is because we

[jira] [Updated] (PHOENIX-2596) Asynchronous Local Index is not available

[ https://issues.apache.org/jira/browse/PHOENIX-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-2596: - Attachment: PHOENIX-2596.patch It's not just a local index problem it's

Re: Are we ready for 4.8.0 RC?

Oh great...It seems ,they are very close to completion and will surely add significant value to the release. On Wed, Jun 1, 2016 at 5:10 AM, Samarth Jain wrote: > There are a few issues that I am working on currently that I hope to have > fixes for by early next week: >

[jira] [Commented] (PHOENIX-2934) Checking a coerce expression at top level should not be necessary for Union All query

[ https://issues.apache.org/jira/browse/PHOENIX-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309428#comment-15309428 ] Alicia Ying Shu commented on PHOENIX-2934: -- Looked into the codes, the issue was caused by

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309418#comment-15309418 ] Lars Hofhansl commented on PHOENIX-258: --- Actually before we pull the trigger I want to add an

[jira] [Updated] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-258: -- Attachment: 258-v13.txt -v13 * fixes reverse scans for fixed length key parts * more tests