[jira] [Updated] (PHOENIX-3113) Automatic build of async index will happen even if mapreduce.framework.name is not set in any configuration

[ https://issues.apache.org/jira/browse/PHOENIX-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-3113: Attachment: PHOENIX-3113-v6.patch > Automatic build of async index will happen even if

[jira] [Commented] (PHOENIX-3113) Automatic build of async index will happen even if mapreduce.framework.name is not set in any configuration

[ https://issues.apache.org/jira/browse/PHOENIX-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395093#comment-15395093 ] Thomas D'Silva commented on PHOENIX-3113: - I will create a separate JIRA to fix

[jira] [Commented] (PHOENIX-3113) Automatic build of async index will happen even if mapreduce.framework.name is not set in any configuration

[ https://issues.apache.org/jira/browse/PHOENIX-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395064#comment-15395064 ] James Taylor commented on PHOENIX-3113: --- I couldn't find anywhere in IndexTool where we were

[jira] [Commented] (PHOENIX-3113) Automatic build of async index will happen even if mapreduce.framework.name is not set in any configuration

[ https://issues.apache.org/jira/browse/PHOENIX-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395054#comment-15395054 ] Thomas D'Silva commented on PHOENIX-3113: - Its failing because the number of rows in the index

[jira] [Commented] (PHOENIX-3113) Automatic build of async index will happen even if mapreduce.framework.name is not set in any configuration

[ https://issues.apache.org/jira/browse/PHOENIX-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395022#comment-15395022 ] James Taylor commented on PHOENIX-3113: --- Where/how does it fail? This is the first time it's been

[jira] [Commented] (PHOENIX-3113) Automatic build of async index will happen even if mapreduce.framework.name is not set in any configuration

[ https://issues.apache.org/jira/browse/PHOENIX-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395010#comment-15395010 ] Thomas D'Silva commented on PHOENIX-3113: - ImmutableIndexIT.testCreateIndexWhileUpsertingData

[jira] [Commented] (PHOENIX-3113) Automatic build of async index will happen even if mapreduce.framework.name is not set in any configuration

[ https://issues.apache.org/jira/browse/PHOENIX-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394908#comment-15394908 ] James Taylor commented on PHOENIX-3113: --- +1. Nice work [~singamteja] & [~tdsilva]. Thanks for

[jira] [Updated] (PHOENIX-3113) Automatic build of async index will happen even if mapreduce.framework.name is not set in any configuration

[ https://issues.apache.org/jira/browse/PHOENIX-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-3113: Attachment: PHOENIX-3113-v5.patch [~jamestaylor] Sorry about that, I have attached a

[jira] [Updated] (PHOENIX-3113) Automatic build of async index will happen even if mapreduce.framework.name is not set in any configuration

[ https://issues.apache.org/jira/browse/PHOENIX-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-3113: Attachment: PHOENIX-3113-v4.patch [~jamestaylor] Can you please review? I modified

[jira] [Resolved] (PHOENIX-3096) Explain command is raising an ArithmeticException

[ https://issues.apache.org/jira/browse/PHOENIX-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alicia Ying Shu resolved PHOENIX-3096. -- Resolution: Won't Fix > Explain command is raising an ArithmeticException >

[jira] [Commented] (PHOENIX-3096) Explain command is raising an ArithmeticException

[ https://issues.apache.org/jira/browse/PHOENIX-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394506#comment-15394506 ] Alicia Ying Shu commented on PHOENIX-3096: -- The codes have been changed. No longer valid. >

[jira] [Commented] (PHOENIX-3113) Automatic build of async index will happen even if mapreduce.framework.name is not set in any configuration

[ https://issues.apache.org/jira/browse/PHOENIX-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394502#comment-15394502 ] James Taylor commented on PHOENIX-3113: --- Actually, my bad, the test that sets the property to

[jira] [Commented] (PHOENIX-3113) Automatic build of async index will happen even if mapreduce.framework.name is not set in any configuration

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

[jira] [Commented] (PHOENIX-3119) Setup of mini cluster after tear down still applies older cluster configs in BaseTest.java

[ https://issues.apache.org/jira/browse/PHOENIX-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394109#comment-15394109 ] Loknath Priyatham Teja Singamsetty commented on PHOENIX-3119: -- Got it.

[jira] [Commented] (PHOENIX-3113) Automatic build of async index will happen even if mapreduce.framework.name is not set in any configuration

[ https://issues.apache.org/jira/browse/PHOENIX-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394103#comment-15394103 ] Loknath Priyatham Teja Singamsetty commented on PHOENIX-3113: --

[jira] [Updated] (PHOENIX-3113) Automatic build of async index will happen even if mapreduce.framework.name is not set in any configuration

[ https://issues.apache.org/jira/browse/PHOENIX-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Loknath Priyatham Teja Singamsetty updated PHOENIX-3113: - Attachment: phoenix-3113-v2.patch > Automatic

[jira] [Commented] (PHOENIX-2900) Unable to find hash cache once a salted table 's first region has split

[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393937#comment-15393937 ] James Taylor commented on PHOENIX-2900: --- Great, glad to hear everything is working now. There were

[jira] [Commented] (PHOENIX-3113) Automatic build of async index will happen even if mapreduce.framework.name is not set in any configuration

[ https://issues.apache.org/jira/browse/PHOENIX-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393927#comment-15393927 ] James Taylor commented on PHOENIX-3113: --- Create a separate unit test to test

[jira] [Commented] (PHOENIX-3119) Setup of mini cluster after tear down still applies older cluster configs in BaseTest.java

[ https://issues.apache.org/jira/browse/PHOENIX-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393691#comment-15393691 ] Loknath Priyatham Teja Singamsetty commented on PHOENIX-3119: --

[jira] [Commented] (PHOENIX-3113) Automatic build of async index will happen even if mapreduce.framework.name is not set in any configuration

[ https://issues.apache.org/jira/browse/PHOENIX-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393657#comment-15393657 ] Loknath Priyatham Teja Singamsetty commented on PHOENIX-3113: -- The

[jira] [Assigned] (PHOENIX-3119) Setup of mini cluster after tear down still applies older cluster configs in BaseTest.java

[ https://issues.apache.org/jira/browse/PHOENIX-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Loknath Priyatham Teja Singamsetty reassigned PHOENIX-3119: Assignee: Loknath Priyatham Teja

[jira] [Created] (PHOENIX-3119) Setup of mini cluster after tear down still applies older cluster configs in BaseTest.java

Loknath Priyatham Teja Singamsetty created PHOENIX-3119: Summary: Setup of mini cluster after tear down still applies older cluster configs in BaseTest.java Key: PHOENIX-3119 URL:

[jira] [Comment Edited] (PHOENIX-2900) Unable to find hash cache once a salted table 's first region has split

[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393485#comment-15393485 ] chenglei edited comment on PHOENIX-2900 at 7/26/16 9:39 AM: [~jamestaylor],

[jira] [Comment Edited] (PHOENIX-2900) Unable to find hash cache once a salted table 's first region has split

[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393485#comment-15393485 ] chenglei edited comment on PHOENIX-2900 at 7/26/16 9:26 AM: [~jamestaylor],

[jira] [Comment Edited] (PHOENIX-2900) Unable to find hash cache once a salted table 's first region has split

[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393485#comment-15393485 ] chenglei edited comment on PHOENIX-2900 at 7/26/16 9:15 AM: [~jamestaylor],

[jira] [Comment Edited] (PHOENIX-2900) Unable to find hash cache once a salted table 's first region has split

[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393485#comment-15393485 ] chenglei edited comment on PHOENIX-2900 at 7/26/16 9:14 AM: [~jamestaylor],

[jira] [Comment Edited] (PHOENIX-2900) Unable to find hash cache once a salted table 's first region has split

[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393485#comment-15393485 ] chenglei edited comment on PHOENIX-2900 at 7/26/16 9:14 AM: [~jamestaylor],

[jira] [Commented] (PHOENIX-2900) Unable to find hash cache once a salted table 's first region has split

[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393485#comment-15393485 ] chenglei commented on PHOENIX-2900: --- [~jamestaylor], sorry for delayed response. Yes.when the