[jira] [Comment Edited] (PHOENIX-4083) Incorrect conditional when including OFFSET into explain plan

[ https://issues.apache.org/jira/browse/PHOENIX-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128594#comment-16128594 ] Ankit Singhal edited comment on PHOENIX-4083 at 8/16/17 10:14 AM: -- yes

[jira] [Commented] (PHOENIX-4083) Incorrect conditional when including OFFSET into explain plan

[ https://issues.apache.org/jira/browse/PHOENIX-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128594#comment-16128594 ] Ankit Singhal commented on PHOENIX-4083: yes.. my bad. Thanks [~lifove] for pointing out. Just

[jira] [Resolved] (PHOENIX-4069) When use row timestamp table,del row1 by 'delete from table' , and I get failed by upsert row1 into the table.

[ https://issues.apache.org/jira/browse/PHOENIX-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-4069. Resolution: Won't Fix > When use row timestamp table,del row1 by 'delete from ta

[jira] [Commented] (PHOENIX-4069) When use row timestamp table,del row1 by 'delete from table' , and I get failed by upsert row1 into the table.

[ https://issues.apache.org/jira/browse/PHOENIX-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119466#comment-16119466 ] Ankit Singhal commented on PHOENIX-4069: It is as per HBase semantics, so if you have row

[jira] [Commented] (PHOENIX-3987) Do not read index when Select All in case of index scan.

[ https://issues.apache.org/jira/browse/PHOENIX-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098548#comment-16098548 ] Ankit Singhal commented on PHOENIX-3987: Thanks [~mini666] for finding the root cause

[jira] [Comment Edited] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091744#comment-16091744 ] Ankit Singhal edited comment on PHOENIX-4010 at 7/18/17 3:54 PM

[jira] [Commented] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091744#comment-16091744 ] Ankit Singhal commented on PHOENIX-4010: ping [~giacomotaylor] for the review. > Hash J

[jira] [Comment Edited] (PHOENIX-4033) Limit number of rows instead of time period for partial index rebuilder

[ https://issues.apache.org/jira/browse/PHOENIX-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091195#comment-16091195 ] Ankit Singhal edited comment on PHOENIX-4033 at 7/18/17 3:50 PM: - yeah

[jira] [Updated] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: PHOENIX-4010_v2_rebased_1.patch > Hash Join cache may not be send to

[jira] [Updated] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: PHOENIX-4010_v2_rebased.patch > Hash Join cache may not be send to

[jira] [Updated] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: (was: PHOENIX-4010_v2_rebased.patch) > Hash Join cache may not be s

[jira] [Commented] (PHOENIX-4033) Limit number of rows instead of time period for partial index rebuilder

[ https://issues.apache.org/jira/browse/PHOENIX-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091195#comment-16091195 ] Ankit Singhal commented on PHOENIX-4033: yeah, the goal was to do the rebuild the indexes

[jira] [Comment Edited] (PHOENIX-4018) HashJoin may produce nulls for LHS table columns

[ https://issues.apache.org/jira/browse/PHOENIX-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089865#comment-16089865 ] Ankit Singhal edited comment on PHOENIX-4018 at 7/17/17 2:05 PM: - Yes

[jira] [Commented] (PHOENIX-4018) HashJoin may produce nulls for LHS table columns

[ https://issues.apache.org/jira/browse/PHOENIX-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089865#comment-16089865 ] Ankit Singhal commented on PHOENIX-4018: Yes, only last scanner should update the progress(which

[jira] [Updated] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: PHOENIX-4010_v2_rebased.patch > Hash Join cache may not be send to

[jira] [Commented] (PHOENIX-3163) Split during global index creation may cause ERROR 201 error.

[ https://issues.apache.org/jira/browse/PHOENIX-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089582#comment-16089582 ] Ankit Singhal commented on PHOENIX-3163: It is getting reproduced

[jira] [Updated] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: PHOENIX-4010_v2.patch > Hash Join cache may not be send to all regionserv

[jira] [Commented] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089565#comment-16089565 ] Ankit Singhal commented on PHOENIX-4010: Thanks [~giacomotaylor] and [~sergey.soldatov] . I have

[jira] [Commented] (PHOENIX-4018) HashJoin may produce nulls for LHS table columns

[ https://issues.apache.org/jira/browse/PHOENIX-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16087074#comment-16087074 ] Ankit Singhal commented on PHOENIX-4018: Thanks, [~sergey.soldatov] for the patch. The problem

[jira] [Commented] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086911#comment-16086911 ] Ankit Singhal commented on PHOENIX-4010: Thanks [~sergey.soldatov] and [~giacomotaylor

[jira] [Comment Edited] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086031#comment-16086031 ] Ankit Singhal edited comment on PHOENIX-4010 at 7/13/17 5:25 PM

[jira] [Updated] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: PHOENIX-4010_v1.patch Extended last patch with :- * Limit memory for hash join

[jira] [Comment Edited] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086031#comment-16086031 ] Ankit Singhal edited comment on PHOENIX-4010 at 7/13/17 5:21 PM

[jira] [Updated] (PHOENIX-3475) MetaData #getTables() API doesn't return view indexes

[ https://issues.apache.org/jira/browse/PHOENIX-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3475: --- Fix Version/s: (was: 4.9.0) 4.12.0 > MetaData #getTables()

[jira] [Updated] (PHOENIX-3956) NTH_VALUE(R.NAME,2) return null

[ https://issues.apache.org/jira/browse/PHOENIX-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3956: --- Fix Version/s: (was: 4.9.0) 4.12.0 > NTH_VALUE(R.NAME,2) return n

[jira] [Updated] (PHOENIX-3454) ON DUPLICATE KEY construct doesn't work correctly when using lower case column names

[ https://issues.apache.org/jira/browse/PHOENIX-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3454: --- Fix Version/s: (was: 4.9.0) 4.12.0 > ON DUPLICATE KEY constr

[jira] [Updated] (PHOENIX-3507) HBase secure wal log cash with Phoenix secondary index

[ https://issues.apache.org/jira/browse/PHOENIX-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3507: --- Fix Version/s: (was: 4.9.0) 4.12.0 > HBase secure wal log c

[jira] [Updated] (PHOENIX-3655) Metrics for PQS

[ https://issues.apache.org/jira/browse/PHOENIX-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3655: --- Fix Version/s: (was: 4.9.0) 4.12.0 > Metrics for

[jira] [Resolved] (PHOENIX-3501) Push limit to server for distinct optimization

[ https://issues.apache.org/jira/browse/PHOENIX-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3501. Resolution: Fixed > Push limit to server for distinct optimizat

[jira] [Resolved] (PHOENIX-3457) Adjust build settings in pom to improve consistency

[ https://issues.apache.org/jira/browse/PHOENIX-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3457. Resolution: Fixed > Adjust build settings in pom to improve consiste

[jira] [Commented] (PHOENIX-3501) Push limit to server for distinct optimization

[ https://issues.apache.org/jira/browse/PHOENIX-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085533#comment-16085533 ] Ankit Singhal commented on PHOENIX-3501: [~giacomotaylor], if this is committed already in 4.9.0

[jira] [Commented] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16083739#comment-16083739 ] Ankit Singhal commented on PHOENIX-4010: While implementing, I found that there is a problem

[jira] [Created] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

Ankit Singhal created PHOENIX-4010: -- Summary: Hash Join cache may not be send to all regionservers when we have stale HBase meta cache Key: PHOENIX-4010 URL: https://issues.apache.org/jira/browse/PHOENIX-4010

[jira] [Updated] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: (was: PHOENIX-4010.patch) > Hash Join cache may not be send to

[jira] [Updated] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: PHOENIX-4010.patch > Hash Join cache may not be send to all regionservers w

[jira] [Updated] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: (was: PHOENIX-4010.patch) > Hash Join cache may not be send to

[jira] [Updated] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: PHOENIX-4010.patch > Hash Join cache may not be send to all regionservers w

[jira] [Updated] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: (was: PHOENIX-4010.patch) > Hash Join cache may not be send to

[jira] [Commented] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16082289#comment-16082289 ] Ankit Singhal commented on PHOENIX-4010: One option (discussed internally with [~devaraj

[jira] [Updated] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

[ https://issues.apache.org/jira/browse/PHOENIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: PHOENIX-4010.patch > Hash Join cache may not be send to all regionservers w

[jira] [Commented] (PHOENIX-3944) ReadOnlyTableException occurs when we map Phoenix view to an existing HBase table with Namespace Mapping enabled

[ https://issues.apache.org/jira/browse/PHOENIX-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16077986#comment-16077986 ] Ankit Singhal commented on PHOENIX-3944: Thanks [~brfrn169] for the fix. Committed to master

[jira] [Comment Edited] (PHOENIX-3997) UngroupedAggregateRegionObserver.commitBatchWithHTable() should not check the memstore size and wait for flush.

[ https://issues.apache.org/jira/browse/PHOENIX-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16077629#comment-16077629 ] Ankit Singhal edited comment on PHOENIX-3997 at 7/7/17 10:35 AM: - \+1

[jira] [Commented] (PHOENIX-3944) ReadOnlyTableException occurs when we map Phoenix view to an existing HBase table with Namespace Mapping enabled

[ https://issues.apache.org/jira/browse/PHOENIX-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16077936#comment-16077936 ] Ankit Singhal commented on PHOENIX-3944: [~brfrn169], yep, MutableIndexFailureIT is not related

[jira] [Commented] (PHOENIX-3997) UngroupedAggregateRegionObserver.commitBatchWithHTable() should not check the memstore size and wait for flush.

[ https://issues.apache.org/jira/browse/PHOENIX-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16077629#comment-16077629 ] Ankit Singhal commented on PHOENIX-3997: 1 for removing the code for wait for a flush from

[jira] [Resolved] (PHOENIX-3502) Support ARRAY DML in Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3502. Resolution: Fixed > Support ARRAY DML in Calcite-Phoe

[jira] [Resolved] (PHOENIX-3882) Support Array functions

[ https://issues.apache.org/jira/browse/PHOENIX-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3882. Resolution: Fixed > Support Array functi

[jira] [Commented] (PHOENIX-3360) Secondary index configuration is wrong

[ https://issues.apache.org/jira/browse/PHOENIX-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074871#comment-16074871 ] Ankit Singhal commented on PHOENIX-3360: I think this can be included as a part of our release

[jira] [Commented] (PHOENIX-3360) Secondary index configuration is wrong

[ https://issues.apache.org/jira/browse/PHOENIX-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074699#comment-16074699 ] Ankit Singhal commented on PHOENIX-3360: [~sergey.soldatov], would you mind opening a new JIRA

[jira] [Commented] (PHOENIX-3944) ReadOnlyTableException occurs when we map Phoenix view to an existing HBase table with Namespace Mapping enabled

[ https://issues.apache.org/jira/browse/PHOENIX-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074681#comment-16074681 ] Ankit Singhal commented on PHOENIX-3944: bq. I attached new patch but applying the patch

[jira] [Commented] (PHOENIX-3944) ReadOnlyTableException occurs when we map Phoenix view to an existing HBase table with Namespace Mapping enabled

[ https://issues.apache.org/jira/browse/PHOENIX-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073495#comment-16073495 ] Ankit Singhal commented on PHOENIX-3944: [~brfrn169], there are some test cases failing, can you

[jira] [Commented] (PHOENIX-3986) UngroupedAggregateRegionObserver.commitBatch() should set the index metadata as an attribute on every mutation

[ https://issues.apache.org/jira/browse/PHOENIX-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073494#comment-16073494 ] Ankit Singhal commented on PHOENIX-3986: [~tdsilva], I think you are right

[jira] [Updated] (PHOENIX-3944) ReadOnlyTableException occurs when we map Phoenix view to an existing HBase table with Namespace Mapping enabled

[ https://issues.apache.org/jira/browse/PHOENIX-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3944: --- Attachment: PHOENIX-3944_v3_4.x_HBase-1.2.patch > ReadOnlyTableException occurs when we

[jira] [Updated] (PHOENIX-3944) ReadOnlyTableException occurs when we map Phoenix view to an existing HBase table with Namespace Mapping enabled

[ https://issues.apache.org/jira/browse/PHOENIX-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3944: --- Attachment: PHOENIX-3944_v3.patch > ReadOnlyTableException occurs when we map Phoenix v

[jira] [Updated] (PHOENIX-3944) ReadOnlyTableException occurs when we map Phoenix view to an existing HBase table with Namespace Mapping enabled

[ https://issues.apache.org/jira/browse/PHOENIX-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3944: --- Attachment: PHOENIX-3944_v2.patch Thanks [~brfrn169], but Jenkins requires a different name

[jira] [Commented] (PHOENIX-3944) ReadOnlyTableException occurs when we map Phoenix view to an existing HBase table with Namespace Mapping enabled

[ https://issues.apache.org/jira/browse/PHOENIX-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16066459#comment-16066459 ] Ankit Singhal commented on PHOENIX-3944: yes [~brfrn169], can you please upload the patch after

[jira] [Assigned] (PHOENIX-3944) ReadOnlyTableException occurs when we map Phoenix view to an existing HBase table with Namespace Mapping enabled

[ https://issues.apache.org/jira/browse/PHOENIX-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reassigned PHOENIX-3944: -- Assignee: Toshihiro Suzuki > ReadOnlyTableException occurs when we map Phoenix v

[jira] [Updated] (PHOENIX-3944) ReadOnlyTableException occurs when we map Phoenix view to an existing HBase table with Namespace Mapping enabled

[ https://issues.apache.org/jira/browse/PHOENIX-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3944: --- Attachment: PHOENIX-3944.patch > ReadOnlyTableException occurs when we map Phoenix v

[jira] [Assigned] (PHOENIX-3633) null pointer exception when subsquery for not exists returns empty result set

[ https://issues.apache.org/jira/browse/PHOENIX-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reassigned PHOENIX-3633: -- Assignee: Jerry He (was: NIDHI GAMBHIR) > null pointer exception when subsqu

[jira] [Resolved] (PHOENIX-3959) Unable to create new schema

[ https://issues.apache.org/jira/browse/PHOENIX-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3959. Resolution: Invalid You may refer the docs(https://phoenix.apache.org

[jira] [Resolved] (PHOENIX-3966) Failed to move working directory snapshot { ss=_UPGRADING_TABLE_SYSTEM.MUTEX table=SYSTEM.MUTEX type=DISABLED }

[ https://issues.apache.org/jira/browse/PHOENIX-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3966. Resolution: Duplicate > Failed to move working directory snapshot {

[jira] [Commented] (PHOENIX-3966) Failed to move working directory snapshot { ss=_UPGRADING_TABLE_SYSTEM.MUTEX table=SYSTEM.MUTEX type=DISABLED }

[ https://issues.apache.org/jira/browse/PHOENIX-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064322#comment-16064322 ] Ankit Singhal commented on PHOENIX-3966: Duplicate of PHOENIX-3962. [~vishalb.e...@gmail.com

[jira] [Commented] (PHOENIX-3967) Failed to move working directory snapshot { ss=_UPGRADING_TABLE_SYSTEM.MUTEX table=SYSTEM.MUTEX type=DISABLED }

[ https://issues.apache.org/jira/browse/PHOENIX-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064320#comment-16064320 ] Ankit Singhal commented on PHOENIX-3967: Duplicate of PHOENIX-3962. > Failed to move work

[jira] [Resolved] (PHOENIX-3967) Failed to move working directory snapshot { ss=_UPGRADING_TABLE_SYSTEM.MUTEX table=SYSTEM.MUTEX type=DISABLED }

[ https://issues.apache.org/jira/browse/PHOENIX-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3967. Resolution: Duplicate > Failed to move working directory snapshot {

[jira] [Commented] (PHOENIX-3964) Index.preWALRestore should handle index write failure

[ https://issues.apache.org/jira/browse/PHOENIX-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064183#comment-16064183 ] Ankit Singhal commented on PHOENIX-3964: Thanks [~comnetwork] for the explanation. you are right

[jira] [Comment Edited] (PHOENIX-3964) Index.preWALRestore should handle index write failure

[ https://issues.apache.org/jira/browse/PHOENIX-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060859#comment-16060859 ] Ankit Singhal edited comment on PHOENIX-3964 at 6/23/17 1:14 PM: - bq

[jira] [Commented] (PHOENIX-3964) Index.preWALRestore should handle index write failure

[ https://issues.apache.org/jira/browse/PHOENIX-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060859#comment-16060859 ] Ankit Singhal commented on PHOENIX-3964: bq. PHOENIX-3072 only handle the index regions which

[jira] [Comment Edited] (PHOENIX-3964) Index.preWALRestore should handle index write failure

[ https://issues.apache.org/jira/browse/PHOENIX-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060859#comment-16060859 ] Ankit Singhal edited comment on PHOENIX-3964 at 6/23/17 1:06 PM: - bq

[jira] [Commented] (PHOENIX-3964) Index.preWALRestore should handle index write failure

[ https://issues.apache.org/jira/browse/PHOENIX-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060608#comment-16060608 ] Ankit Singhal commented on PHOENIX-3964: +1, it completely makes sense. Thanks [~comnetwork

[jira] [Updated] (PHOENIX-3973) Immutable tables using encoding are failing in phoenix-calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3973: --- Labels: calcite (was: ) > Immutable tables using encoding are failing in phoenix-calc

[jira] [Resolved] (PHOENIX-3973) Immutable tables using encoding are failing in phoenix-calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3973. Resolution: Fixed > Immutable tables using encoding are failing in phoenix-calc

[jira] [Updated] (PHOENIX-3973) Immutable tables using encoding are failing in phoenix-calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3973: --- Attachment: PHOENIX-3973.patch > Immutable tables using encoding are failing in phoe

[jira] [Created] (PHOENIX-3973) Immutable tables using encoding are failing in phoenix-calcite

Ankit Singhal created PHOENIX-3973: -- Summary: Immutable tables using encoding are failing in phoenix-calcite Key: PHOENIX-3973 URL: https://issues.apache.org/jira/browse/PHOENIX-3973 Project

[jira] [Deleted] (PHOENIX-3596) CREATE TABLE with immutable rows property is failing in Phoenix-Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal deleted PHOENIX-3596: --- > CREATE TABLE with immutable rows property is failing in Phoenix-Calc

[jira] [Deleted] (PHOENIX-3595) CREATE TABLE with immutable rows property is failing in Phoenix-Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal deleted PHOENIX-3595: --- > CREATE TABLE with immutable rows property is failing in Phoenix-Calc

[jira] [Deleted] (PHOENIX-3593) CREATE TABLE with immutable rows property is failing in Phoenix-Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal deleted PHOENIX-3593: --- > CREATE TABLE with immutable rows property is failing in Phoenix-Calc

[jira] [Deleted] (PHOENIX-3597) CREATE TABLE with immutable rows property is failing in Phoenix-Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal deleted PHOENIX-3597: --- > CREATE TABLE with immutable rows property is failing in Phoenix-Calc

[jira] [Assigned] (PHOENIX-3597) CREATE TABLE with immutable rows property is failing in Phoenix-Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reassigned PHOENIX-3597: -- Assignee: (was: Rajeshbabu Chintaguntla) > CREATE TABLE with immutable r

[jira] [Comment Edited] (PHOENIX-3962) Not creating the table in custom schema

[ https://issues.apache.org/jira/browse/PHOENIX-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057037#comment-16057037 ] Ankit Singhal edited comment on PHOENIX-3962 at 6/21/17 6:07 AM

[jira] [Commented] (PHOENIX-3962) Not creating the table in custom schema

[ https://issues.apache.org/jira/browse/PHOENIX-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057037#comment-16057037 ] Ankit Singhal commented on PHOENIX-3962: Not sure why local filesystem causing any exception

[jira] [Commented] (PHOENIX-3962) Not creating the table in custom schema

[ https://issues.apache.org/jira/browse/PHOENIX-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056988#comment-16056988 ] Ankit Singhal commented on PHOENIX-3962: It seems error while creating SYSTEM.MUTEX snapshot

[jira] [Commented] (PHOENIX-3898) Empty result set after split with local index on multi-tenant table

[ https://issues.apache.org/jira/browse/PHOENIX-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043816#comment-16043816 ] Ankit Singhal commented on PHOENIX-3898: bq. That's a bit strange to query the index table

[jira] [Comment Edited] (PHOENIX-3726) Error while upgrading system tables

[ https://issues.apache.org/jira/browse/PHOENIX-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043270#comment-16043270 ] Ankit Singhal edited comment on PHOENIX-3726 at 6/8/17 7:17 PM

[jira] [Commented] (PHOENIX-3726) Error while upgrading system tables

[ https://issues.apache.org/jira/browse/PHOENIX-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043270#comment-16043270 ] Ankit Singhal commented on PHOENIX-3726: [~bhaveshvv109], you can follow below steps {code

[jira] [Assigned] (PHOENIX-3917) RowProjector#getEstimatedRowByteSize() returns incorrect value

[ https://issues.apache.org/jira/browse/PHOENIX-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reassigned PHOENIX-3917: -- Assignee: Biju Nair > RowProjector#getEstimatedRowByteSize() returns incorrect va

[jira] [Commented] (PHOENIX-3917) RowProjector#getEstimatedRowByteSize() returns incorrect value

[ https://issues.apache.org/jira/browse/PHOENIX-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041038#comment-16041038 ] Ankit Singhal commented on PHOENIX-3917: Yes [~gsbiju], change make sense to me. > RowProjec

[jira] [Resolved] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3797. Resolution: Fixed > Local Index - Compaction fails on table with local index

[jira] [Commented] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039580#comment-16039580 ] Ankit Singhal commented on PHOENIX-3797: Thanks [~lhofhansl] and [~jamestaylor] for the review

[jira] [Created] (PHOENIX-3916) Repair local index from offline tool

Ankit Singhal created PHOENIX-3916: -- Summary: Repair local index from offline tool Key: PHOENIX-3916 URL: https://issues.apache.org/jira/browse/PHOENIX-3916 Project: Phoenix Issue Type

[jira] [Comment Edited] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037323#comment-16037323 ] Ankit Singhal edited comment on PHOENIX-3797 at 6/5/17 6:27 PM: bq. Can

[jira] [Commented] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037323#comment-16037323 ] Ankit Singhal commented on PHOENIX-3797: bq. Can we optionally disable the index? I'd

[jira] [Commented] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16034641#comment-16034641 ] Ankit Singhal commented on PHOENIX-3797: [~jamestaylor], I'm not sure if we agreed

[jira] [Updated] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3797: --- Attachment: PHOENIX-3797_v3.patch > Local Index - Compaction fails on table with lo

[jira] [Comment Edited] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032682#comment-16032682 ] Ankit Singhal edited comment on PHOENIX-3797 at 6/1/17 9:27 AM: bq

[jira] [Commented] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032685#comment-16032685 ] Ankit Singhal commented on PHOENIX-3797: Another problem of doing repair during compaction only

[jira] [Issue Comment Deleted] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3797: --- Comment: was deleted (was: Another problem of doing repair during compaction only

[jira] [Commented] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032682#comment-16032682 ] Ankit Singhal commented on PHOENIX-3797: bq. Actually... Can the same thing happen with just

[jira] [Updated] (PHOENIX-3898) Empty result set after split with local index on multi-tenant table

[ https://issues.apache.org/jira/browse/PHOENIX-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3898: --- Description: While testing encounters this(seems related to PHOENIX-3832):- {code} CREATE

[jira] [Created] (PHOENIX-3898) Empty result set after split with local index on multi-tenant table

Ankit Singhal created PHOENIX-3898: -- Summary: Empty result set after split with local index on multi-tenant table Key: PHOENIX-3898 URL: https://issues.apache.org/jira/browse/PHOENIX-3898 Project

[jira] [Commented] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030139#comment-16030139 ] Ankit Singhal commented on PHOENIX-3797: bq. It also seems fishy to apply the mutations

[jira] [Comment Edited] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16029614#comment-16029614 ] Ankit Singhal edited comment on PHOENIX-3797 at 5/30/17 4:06 PM

<    3   4   5   6   7   8   9   10   11   12   >