[jira] [Commented] (PHOENIX-3383) Comparison between descending row keys used in RVC is reverse
[ https://issues.apache.org/jira/browse/PHOENIX-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534425#comment-16534425 ] James Taylor commented on PHOENIX-3383: --- Thanks, [~tdsilva]. Good find - you're correct. I've fixed this in the current patch and added more tests for that case. > Comparison between descending row keys used in RVC is reverse > - > > Key: PHOENIX-3383 > URL: https://issues.apache.org/jira/browse/PHOENIX-3383 > Project: Phoenix > Issue Type: Bug >Reporter: James Taylor >Assignee: James Taylor >Priority: Major > Labels: DESC > Fix For: 4.15.0 > > Attachments: PHOENIX-3383-wip1.patch, PHOENIX-3383-wip5.patch, > PHOENIX-3383-wip6.patch, PHOENIX-3383-wip7.patch, PHOENIX-3383_v1.patch, > PHOENIX-3383_v2.patch, PHOENIX-3383_v3.patch, PHOENIX-3383_wip.patch, > PHOENIX-3383_wip2.patch, PHOENIX-3383_wip3.patch > > > See PHOENIX-3382, but the comparison for RVC with descending row key columns > is the reverse of what it should be. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-3383) Comparison between descending row keys used in RVC is reverse
[ https://issues.apache.org/jira/browse/PHOENIX-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3383: -- Attachment: PHOENIX-3383_v3.patch > Comparison between descending row keys used in RVC is reverse > - > > Key: PHOENIX-3383 > URL: https://issues.apache.org/jira/browse/PHOENIX-3383 > Project: Phoenix > Issue Type: Bug >Reporter: James Taylor >Assignee: James Taylor >Priority: Major > Labels: DESC > Fix For: 4.15.0 > > Attachments: PHOENIX-3383-wip1.patch, PHOENIX-3383-wip5.patch, > PHOENIX-3383-wip6.patch, PHOENIX-3383-wip7.patch, PHOENIX-3383_v1.patch, > PHOENIX-3383_v2.patch, PHOENIX-3383_v3.patch, PHOENIX-3383_wip.patch, > PHOENIX-3383_wip2.patch, PHOENIX-3383_wip3.patch > > > See PHOENIX-3382, but the comparison for RVC with descending row key columns > is the reverse of what it should be. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (PHOENIX-4797) file not found or file exist exception when create global index use -snaopshot option
[
https://issues.apache.org/jira/browse/PHOENIX-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534394#comment-16534394
]
ASF GitHub Bot commented on PHOENIX-4797:
-
Github user 492066199 commented on the issue:
https://github.com/apache/phoenix/pull/306
Thank you for your advice，I've changed it to use both ”String“ Path api;
> file not found or file exist exception when create global index use
> -snaopshot option
> -
>
> Key: PHOENIX-4797
> URL: https://issues.apache.org/jira/browse/PHOENIX-4797
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.13.2-cdh5.11.2
>Reporter: sailingYang
>Priority: Major
>
> when use indextool with -snapshot option and if the mapreduce create multi
> mapper.this will cause the hdfs file not found or hdfs file exist
> exception。finally the mapreduce task must be failed. because the mapper use
> the same restore work dir.
> {code:java}
> Error: java.io.IOException: java.util.concurrent.ExecutionException:
> java.io.IOException: The specified region already exists on disk:
> hdfs://m12v1.mlamp.cn:8020/tmp/index-snapshot-dir/restore-dir/e738c85b-2394-43fc-b9de-b8280bc329ca/data/default/SCOPA.CETUS_EVENT_ZY_SCOPA_31_0516_TRAIN_EVENT/2ab2c1d73d2e31bb5a5e2b394da564f8
> at
> org.apache.hadoop.hbase.util.ModifyRegionUtils.createRegions(ModifyRegionUtils.java:186)
> at
> org.apache.hadoop.hbase.snapshot.RestoreSnapshotHelper.cloneHdfsRegions(RestoreSnapshotHelper.java:578)
> at
> org.apache.hadoop.hbase.snapshot.RestoreSnapshotHelper.restoreHdfsRegions(RestoreSnapshotHelper.java:249)
> at
> org.apache.hadoop.hbase.snapshot.RestoreSnapshotHelper.restoreHdfsRegions(RestoreSnapshotHelper.java:171)
> at
> org.apache.hadoop.hbase.snapshot.RestoreSnapshotHelper.copySnapshotForScanner(RestoreSnapshotHelper.java:814)
> at
> org.apache.phoenix.iterate.TableSnapshotResultIterator.init(TableSnapshotResultIterator.java:77)
> at
> org.apache.phoenix.iterate.TableSnapshotResultIterator.(TableSnapshotResultIterator.java:73)
> at
> org.apache.phoenix.mapreduce.PhoenixRecordReader.initialize(PhoenixRecordReader.java:126)
> at
> org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.initialize(MapTask.java:548)
> at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:786)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:164)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: The
> specified region already exists on disk:
> hdfs://m12v1.mlamp.cn:8020/tmp/index-snapshot-dir/restore-dir/e738c85b-2394-43fc-b9de-b8280bc329ca/data/default/SCOPA.CETUS_EVENT_ZY_SCOPA_31_0516_TRAIN_EVENT/2ab2c1d73d2e31bb5a5e2b394da564f8
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:188)
> at
> org.apache.hadoop.hbase.util.ModifyRegionUtils.createRegions(ModifyRegionUtils.java:180)
> ... 15 more
> Caused by: java.io.IOException: The specified region already exists on disk:
> hdfs://m12v1.mlamp.cn:8020/tmp/index-snapshot-dir/restore-dir/e738c85b-2394-43fc-b9de-b8280bc329ca/data/default/SCOPA.CETUS_EVENT_ZY_SCOPA_31_0516_TRAIN_EVENT/2ab2c1d73d2e31bb5a5e2b394da564f8
> at
> org.apache.hadoop.hbase.regionserver.HRegionFileSystem.createRegionOnFileSystem(HRegionFileSystem.java:877)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.createHRegion(HRegion.java:6252)
> at
> org.apache.hadoop.hbase.util.ModifyRegionUtils.createRegion(ModifyRegionUtils.java:205)
> at
> org.apache.hadoop.hbase.util.ModifyRegionUtils$1.call(ModifyRegionUtils.java:173)
> at
> org.apache.hadoop.hbase.util.ModifyRegionUtils$1.call(ModifyRegionUtils.java:170)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> 2018-06-28 15:01:55 70909 [main] INFO org.apache.hadoop.mapreduce.Job - Task
> Id : attempt_1530004808977_0011_m_01_0, Status : FAILED
> Error: java.io.IOException: java.util.concurrent.ExecutionException:
> java.io.IOException: The specified region already exists on disk:
> hdfs://m12v1.mlamp.cn:8020/tmp/index-snapshot-dir/resto
[GitHub] phoenix issue #306: PHOENIX-4797 file not found or file exist exception when...
Github user 492066199 commented on the issue: https://github.com/apache/phoenix/pull/306 Thank you for your adviceï¼I've changed it to use both âStringâ Path api; ---
[jira] [Commented] (PHOENIX-4755) Provide an option to plugin custom avatica server config in PQS
[
https://issues.apache.org/jira/browse/PHOENIX-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534314#comment-16534314
]
Karan Mehta commented on PHOENIX-4755:
--
[~elserj] Please review.
Added a test that verifies that {{CustomAuthentication}} is wired up and a
test to verify that default {{AvaticaServerConfigurationFactory}} would return
a null object.
Since 1.12 Avatica is released now, we can bump up the dependency version and
merge these new changes.
> Provide an option to plugin custom avatica server config in PQS
> ---
>
> Key: PHOENIX-4755
> URL: https://issues.apache.org/jira/browse/PHOENIX-4755
> Project: Phoenix
> Issue Type: Improvement
>Reporter: Karan Mehta
>Priority: Major
> Attachments: PHOENIX-4755.001.diff, PHOENIX-4755.002.diff,
> PHOENIX-4755.003.diff
>
>
> CALCITE-2294 Allow customization for {{AvaticaServerConfiguration}} for
> plugging new authentication mechanisms
> Add a new Phoenix level property and provide resolve the class using
> {{InstanceResolver}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (PHOENIX-4755) Provide an option to plugin custom avatica server config in PQS
[
https://issues.apache.org/jira/browse/PHOENIX-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karan Mehta updated PHOENIX-4755:
-
Attachment: PHOENIX-4755.003.diff
> Provide an option to plugin custom avatica server config in PQS
> ---
>
> Key: PHOENIX-4755
> URL: https://issues.apache.org/jira/browse/PHOENIX-4755
> Project: Phoenix
> Issue Type: Improvement
>Reporter: Karan Mehta
>Priority: Major
> Attachments: PHOENIX-4755.001.diff, PHOENIX-4755.002.diff,
> PHOENIX-4755.003.diff
>
>
> CALCITE-2294 Allow customization for {{AvaticaServerConfiguration}} for
> plugging new authentication mechanisms
> Add a new Phoenix level property and provide resolve the class using
> {{InstanceResolver}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-3383) Comparison between descending row keys used in RVC is reverse
[
https://issues.apache.org/jira/browse/PHOENIX-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534032#comment-16534032
]
Thomas D'Silva commented on PHOENIX-3383:
-
[~jamestaylor] I am reviewing the patch. I had a question about
WhereOptimizerTest.testTrimTrailing(). Since the where clause is (A,B,C) >=
('A','A','A') and (A,B,C) < ('D','D','D') and (B,C) > ('E','E'), shouldn't the
scan start row be "AEF" ?
> Comparison between descending row keys used in RVC is reverse
> -
>
> Key: PHOENIX-3383
> URL: https://issues.apache.org/jira/browse/PHOENIX-3383
> Project: Phoenix
> Issue Type: Bug
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Labels: DESC
> Fix For: 4.15.0
>
> Attachments: PHOENIX-3383-wip1.patch, PHOENIX-3383-wip5.patch,
> PHOENIX-3383-wip6.patch, PHOENIX-3383-wip7.patch, PHOENIX-3383_v1.patch,
> PHOENIX-3383_v2.patch, PHOENIX-3383_wip.patch, PHOENIX-3383_wip2.patch,
> PHOENIX-3383_wip3.patch
>
>
> See PHOENIX-3382, but the comparison for RVC with descending row key columns
> is the reverse of what it should be.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PHOENIX-4797) file not found or file exist exception when create global index use -snaopshot option
[
https://issues.apache.org/jira/browse/PHOENIX-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16533828#comment-16533828
]
ASF GitHub Bot commented on PHOENIX-4797:
-
Github user karanmehta93 commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/306#discussion_r200400417
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/iterate/TableSnapshotResultIterator.java
---
@@ -65,7 +66,8 @@ public TableSnapshotResultIterator(Configuration
configuration, Scan scan, ScanM
this.scan = scan;
this.scanMetricsHolder = scanMetricsHolder;
this.scanIterator = UNINITIALIZED_SCANNER;
-this.restoreDir = new
Path(configuration.get(PhoenixConfigurationUtil.RESTORE_DIR_KEY));
+this.restoreDir = new Path(new
Path(configuration.get(PhoenixConfigurationUtil.RESTORE_DIR_KEY)),
--- End diff --
`Path` also offers other API at
https://hadoop.apache.org/docs/r2.8.2/api/org/apache/hadoop/fs/Path.html
You can specify both of the params as `String`
> file not found or file exist exception when create global index use
> -snaopshot option
> -
>
> Key: PHOENIX-4797
> URL: https://issues.apache.org/jira/browse/PHOENIX-4797
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.13.2-cdh5.11.2
>Reporter: sailingYang
>Priority: Major
>
> when use indextool with -snapshot option and if the mapreduce create multi
> mapper.this will cause the hdfs file not found or hdfs file exist
> exception。finally the mapreduce task must be failed. because the mapper use
> the same restore work dir.
> {code:java}
> Error: java.io.IOException: java.util.concurrent.ExecutionException:
> java.io.IOException: The specified region already exists on disk:
> hdfs://m12v1.mlamp.cn:8020/tmp/index-snapshot-dir/restore-dir/e738c85b-2394-43fc-b9de-b8280bc329ca/data/default/SCOPA.CETUS_EVENT_ZY_SCOPA_31_0516_TRAIN_EVENT/2ab2c1d73d2e31bb5a5e2b394da564f8
> at
> org.apache.hadoop.hbase.util.ModifyRegionUtils.createRegions(ModifyRegionUtils.java:186)
> at
> org.apache.hadoop.hbase.snapshot.RestoreSnapshotHelper.cloneHdfsRegions(RestoreSnapshotHelper.java:578)
> at
> org.apache.hadoop.hbase.snapshot.RestoreSnapshotHelper.restoreHdfsRegions(RestoreSnapshotHelper.java:249)
> at
> org.apache.hadoop.hbase.snapshot.RestoreSnapshotHelper.restoreHdfsRegions(RestoreSnapshotHelper.java:171)
> at
> org.apache.hadoop.hbase.snapshot.RestoreSnapshotHelper.copySnapshotForScanner(RestoreSnapshotHelper.java:814)
> at
> org.apache.phoenix.iterate.TableSnapshotResultIterator.init(TableSnapshotResultIterator.java:77)
> at
> org.apache.phoenix.iterate.TableSnapshotResultIterator.(TableSnapshotResultIterator.java:73)
> at
> org.apache.phoenix.mapreduce.PhoenixRecordReader.initialize(PhoenixRecordReader.java:126)
> at
> org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.initialize(MapTask.java:548)
> at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:786)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:164)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1709)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: The
> specified region already exists on disk:
> hdfs://m12v1.mlamp.cn:8020/tmp/index-snapshot-dir/restore-dir/e738c85b-2394-43fc-b9de-b8280bc329ca/data/default/SCOPA.CETUS_EVENT_ZY_SCOPA_31_0516_TRAIN_EVENT/2ab2c1d73d2e31bb5a5e2b394da564f8
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:188)
> at
> org.apache.hadoop.hbase.util.ModifyRegionUtils.createRegions(ModifyRegionUtils.java:180)
> ... 15 more
> Caused by: java.io.IOException: The specified region already exists on disk:
> hdfs://m12v1.mlamp.cn:8020/tmp/index-snapshot-dir/restore-dir/e738c85b-2394-43fc-b9de-b8280bc329ca/data/default/SCOPA.CETUS_EVENT_ZY_SCOPA_31_0516_TRAIN_EVENT/2ab2c1d73d2e31bb5a5e2b394da564f8
> at
> org.apache.hadoop.hbase.regionserver.HRegionFileSystem.createRegionOnFileSystem(HRegionFileSystem.java:877)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.createHRegion(HRegion.java:6252)
> at
> org.apache.hadoop.hbase.util.ModifyRegionUtils.createRegion(ModifyRegionUtils.java:205)
> at
> org.apache.hadoop.hbase.util.ModifyRegionUtils$1.call(ModifyRegionUtils.java:173)
> at
> org.apache.hadoop.hbase.util.ModifyRegionUtils$1.call(ModifyRegionUtils.java:170)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> a
[GitHub] phoenix pull request #306: PHOENIX-4797 file not found or file exist excepti...
Github user karanmehta93 commented on a diff in the pull request: https://github.com/apache/phoenix/pull/306#discussion_r200400417 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/iterate/TableSnapshotResultIterator.java --- @@ -65,7 +66,8 @@ public TableSnapshotResultIterator(Configuration configuration, Scan scan, ScanM this.scan = scan; this.scanMetricsHolder = scanMetricsHolder; this.scanIterator = UNINITIALIZED_SCANNER; -this.restoreDir = new Path(configuration.get(PhoenixConfigurationUtil.RESTORE_DIR_KEY)); +this.restoreDir = new Path(new Path(configuration.get(PhoenixConfigurationUtil.RESTORE_DIR_KEY)), --- End diff -- `Path` also offers other API at https://hadoop.apache.org/docs/r2.8.2/api/org/apache/hadoop/fs/Path.html You can specify both of the params as `String` ---
Phoenix query tracing issue
We were trying to enable Phoenix query tracing and ran into problem. Traces are not being written to SYSTEM.TRACING_STATS table. We're using HBase 1.3 and Phoenix 4.13.1. We were trying to do this according to this official manual: https://phoenix.apache.org/tracing.html . We've set up hadoop-metrics2-phoenix.properties and hadoop-metrics2-hbase.properties as is from the manual. These files are located at $PHOENIX_HOME/bin/config/hadoop-metrics2-phoenix.properties and $HBASE_HOME/conf/hadoop-metrics2-hbase.properties . hbase-site.xml at $PHOENIX_HOME/bin contains phoenix.trace.frequency property which is set to "always". Despite that when we perform some queries from sqlline.py, traces are not being written to SYSTEM.TRACING_STATS. This table is not even created. During investigation of this problem we dived into Phoenix sources. What confuses us is that we can't find org.apache.phoenix.trace.PhoenixTableMetricsWriter class in sources of Phoenix 4.13.1. Is that correct name of metrics writer class? And what confuses us even more is that turned out that we're specifying unexistent class to HBase, but despite that HBase Master starts and there are no errors in logs. I would expect NoClassDefFoundError or ClassNotFoundException or something like that. Looks like HBase is not even trying to load or instantiate this class. In 4.13.1 org.apache.phoenix.trace.TableWriter class looks like metrics writer class, but after specifying it in phoenix.sink.tracing.writer-class and hbase.sink.tracing.writer-class properties in hadoop-metrics2-phoenix.properties and hadoop-metrics2-hbase.properties there is still no luck: SYSTEM.TRACING_STATS table is not created after we perform some queries in sqlline.py . We've also tried to trace queries performed by our Spark application that uses spark phoenix plugin, but ran into same problem: SYSTEM.TRACING_STATS table is not even initialized. phoenix.trace.frequency = always is specified in HBase config object in our Spark application. Also we've tried to trace queries performed by IntelliJ IDEA via JDBC connection, phoenix.trace.frequency property was set as custom JDBC connection property. Can you please advice what we're doing wrong? Thanks, Stepan.
[jira] [Updated] (PHOENIX-3383) Comparison between descending row keys used in RVC is reverse
[ https://issues.apache.org/jira/browse/PHOENIX-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3383: -- Attachment: PHOENIX-3383_v2.patch > Comparison between descending row keys used in RVC is reverse > - > > Key: PHOENIX-3383 > URL: https://issues.apache.org/jira/browse/PHOENIX-3383 > Project: Phoenix > Issue Type: Bug >Reporter: James Taylor >Assignee: James Taylor >Priority: Major > Labels: DESC > Fix For: 4.15.0 > > Attachments: PHOENIX-3383-wip1.patch, PHOENIX-3383-wip5.patch, > PHOENIX-3383-wip6.patch, PHOENIX-3383-wip7.patch, PHOENIX-3383_v1.patch, > PHOENIX-3383_v2.patch, PHOENIX-3383_wip.patch, PHOENIX-3383_wip2.patch, > PHOENIX-3383_wip3.patch > > > See PHOENIX-3382, but the comparison for RVC with descending row key columns > is the reverse of what it should be. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-3383) Comparison between descending row keys used in RVC is reverse
[ https://issues.apache.org/jira/browse/PHOENIX-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3383: -- Attachment: (was: PHOENIX-3383_v2.patch) > Comparison between descending row keys used in RVC is reverse > - > > Key: PHOENIX-3383 > URL: https://issues.apache.org/jira/browse/PHOENIX-3383 > Project: Phoenix > Issue Type: Bug >Reporter: James Taylor >Assignee: James Taylor >Priority: Major > Labels: DESC > Fix For: 4.15.0 > > Attachments: PHOENIX-3383-wip1.patch, PHOENIX-3383-wip5.patch, > PHOENIX-3383-wip6.patch, PHOENIX-3383-wip7.patch, PHOENIX-3383_v1.patch, > PHOENIX-3383_wip.patch, PHOENIX-3383_wip2.patch, PHOENIX-3383_wip3.patch > > > See PHOENIX-3382, but the comparison for RVC with descending row key columns > is the reverse of what it should be. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-3383) Comparison between descending row keys used in RVC is reverse
[ https://issues.apache.org/jira/browse/PHOENIX-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3383: -- Attachment: PHOENIX-3383_v2.patch > Comparison between descending row keys used in RVC is reverse > - > > Key: PHOENIX-3383 > URL: https://issues.apache.org/jira/browse/PHOENIX-3383 > Project: Phoenix > Issue Type: Bug >Reporter: James Taylor >Assignee: James Taylor >Priority: Major > Labels: DESC > Fix For: 4.15.0 > > Attachments: PHOENIX-3383-wip1.patch, PHOENIX-3383-wip5.patch, > PHOENIX-3383-wip6.patch, PHOENIX-3383-wip7.patch, PHOENIX-3383_v1.patch, > PHOENIX-3383_v2.patch, PHOENIX-3383_wip.patch, PHOENIX-3383_wip2.patch, > PHOENIX-3383_wip3.patch > > > See PHOENIX-3382, but the comparison for RVC with descending row key columns > is the reverse of what it should be. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
