[jira] [Commented] (PHOENIX-2941) Alternative means of propagating schema changes

[ https://issues.apache.org/jira/browse/PHOENIX-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301559#comment-15301559 ] James Taylor commented on PHOENIX-2941: --- The new UPDATE_CACHE_FREQUENCY property[1] available in

[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=15301540#comment-15301540 ] James Taylor commented on PHOENIX-2940: --- To expand on what Josh said, a simple solution since

[jira] [Commented] (PHOENIX-2941) Alternative means of propagating schema changes

[ https://issues.apache.org/jira/browse/PHOENIX-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301473#comment-15301473 ] Andrew Purtell commented on PHOENIX-2941: - Over in HBase we have ZK based notifications like

[jira] [Resolved] (PHOENIX-2910) Avoid synchronous stats lookup in PTable creation while holding row lock

[ https://issues.apache.org/jira/browse/PHOENIX-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved PHOENIX-2910. - Resolution: Duplicate Fix Version/s: (was: 4.8.0) Closing as a dupe in favor of

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

[ https://issues.apache.org/jira/browse/PHOENIX-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser reassigned PHOENIX-2940: --- Assignee: Josh Elser > Remove STATS RPCs from rowlock > -- > >

[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=15301314#comment-15301314 ] Josh Elser commented on PHOENIX-2940: - Nabbing this one for myself after closing PHOENIX-2910 as a

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

[ https://issues.apache.org/jira/browse/PHOENIX-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated PHOENIX-2940: -- Description: We have an unfortunate situation wherein we potentially execute many RPCs while

[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=15301300#comment-15301300 ] Josh Elser commented on PHOENIX-2940: - Linking this over to PHOENIX-2910 since it's (essentially, I

Re: Jenkins build failures?

+1 Great digging, Sergey! Sergey Soldatov wrote: James, Sure. I will file a JIRA and check about non zero thread pool size (not sure that would help since it's initialized in getDefaultExecutor and always used if no other pool is provided in HTable constructor). Thanks, Sergey On Mon, May 23,

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

[ https://issues.apache.org/jira/browse/PHOENIX-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated PHOENIX-2940: -- Summary: Remove STATS RPCs from rowlock (was: Remove CATALOG,STATS RPCs from rowlock)

[jira] [Created] (PHOENIX-2941) Alternative means of propagating schema changes

Nick Dimiduk created PHOENIX-2941: - Summary: Alternative means of propagating schema changes Key: PHOENIX-2941 URL: https://issues.apache.org/jira/browse/PHOENIX-2941 Project: Phoenix Issue

[jira] [Created] (PHOENIX-2940) Remove CATALOG,STATS RPCs from rowlock

Nick Dimiduk created PHOENIX-2940: - Summary: Remove CATALOG,STATS RPCs from rowlock Key: PHOENIX-2940 URL: https://issues.apache.org/jira/browse/PHOENIX-2940 Project: Phoenix Issue Type:

[jira] [Commented] (PHOENIX-2939) MetaCache is easily thrashed with default settings

[ https://issues.apache.org/jira/browse/PHOENIX-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301255#comment-15301255 ] Nick Dimiduk commented on PHOENIX-2939: --- If we want to continue the practice of caching the entire

[jira] [Created] (PHOENIX-2939) MetaCache is easily thrashed with default settings

Nick Dimiduk created PHOENIX-2939: - Summary: MetaCache is easily thrashed with default settings Key: PHOENIX-2939 URL: https://issues.apache.org/jira/browse/PHOENIX-2939 Project: Phoenix

[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-WIP.txt _Work in progress_ patch. Not sure it even compiles. Just parking it

[jira] [Commented] (PHOENIX-2886) Union ALL with Char column not present in the table in Query 1 but in Query 2 throw exception

[ https://issues.apache.org/jira/browse/PHOENIX-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301195#comment-15301195 ] Alicia Ying Shu commented on PHOENIX-2886: -- Need take PChar.INSTANCE from the checking list >

[jira] [Commented] (PHOENIX-2936) Missing antlr runtime on server side after PHOENIX-2908

[ https://issues.apache.org/jira/browse/PHOENIX-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301145#comment-15301145 ] James Taylor commented on PHOENIX-2936: --- +1 on the patch. Thanks, [~sergey.soldatov]! > Missing

[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=15301119#comment-15301119 ] Nick Dimiduk commented on PHOENIX-258: -- In my particular case, itemizing the leading column also

[jira] [Created] (PHOENIX-2938) HFile support for SparkSQL DataFrame saves

Chris Tarnas created PHOENIX-2938: - Summary: HFile support for SparkSQL DataFrame saves Key: PHOENIX-2938 URL: https://issues.apache.org/jira/browse/PHOENIX-2938 Project: Phoenix Issue Type:

[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 ] Nick Dimiduk updated PHOENIX-258: - Attachment: in-clause.png Yes indeed. Here's a rudimentary test result -- my leading column has

[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=15300729#comment-15300729 ] Lars Hofhansl commented on PHOENIX-258: --- [~ndimiduk], FYI. You mentioned you had some stats. Wanna

[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=15300657#comment-15300657 ] Lars Hofhansl commented on PHOENIX-258: --- I'll attempt a combined patch. Should be just using a

[jira] [Commented] (PHOENIX-1734) Local index improvements

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

[jira] [Commented] (PHOENIX-2936) Missing antlr runtime on server side after PHOENIX-2908

[ https://issues.apache.org/jira/browse/PHOENIX-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300231#comment-15300231 ] Sergey Soldatov commented on PHOENIX-2936: -- [~jamestaylor] Runtime only. I checked the server

[jira] [Commented] (PHOENIX-2936) Missing antlr runtime on server side after PHOENIX-2908

[ https://issues.apache.org/jira/browse/PHOENIX-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300059#comment-15300059 ] James Taylor commented on PHOENIX-2936: --- Will this include only antr runtime or all of antlr like

[jira] [Commented] (PHOENIX-2208) Navigation to trace information in tracing UI should be driven off of query instead of trace ID

[ https://issues.apache.org/jira/browse/PHOENIX-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299903#comment-15299903 ] Nishani commented on PHOENIX-2208: --- Hi, An issue is raised if the query is not unique (ex. same

[jira] [Commented] (PHOENIX-2915) Dropping of Index can still leave some non-replayed writes in WAL

[ https://issues.apache.org/jira/browse/PHOENIX-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299836#comment-15299836 ] Rajeshbabu Chintaguntla commented on PHOENIX-2915: -- One more simpler solution would be

[jira] [Updated] (PHOENIX-2915) Dropping of Index can still leave some non-replayed writes in WAL

[ https://issues.apache.org/jira/browse/PHOENIX-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-2915: - Fix Version/s: 4.8.0 > Dropping of Index can still leave some

[jira] [Commented] (PHOENIX-2901) If namespaces are enabled, check for existence of schema when sequence created

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

[jira] [Updated] (PHOENIX-2914) Make sqlline refer to bin/hbase-site.xml by default

[ https://issues.apache.org/jira/browse/PHOENIX-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-2914: - Assignee: Junegunn Choi > Make sqlline refer to bin/hbase-site.xml by

[jira] [Assigned] (PHOENIX-2915) Dropping of Index can still leave some non-replayed writes in WAL

[ https://issues.apache.org/jira/browse/PHOENIX-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reassigned PHOENIX-2915: -- Assignee: Ankit Singhal > Dropping of Index can still leave some non-replayed writes

[jira] [Updated] (PHOENIX-2915) Dropping of Index can still leave some non-replayed writes in WAL

[ https://issues.apache.org/jira/browse/PHOENIX-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-2915: --- Description: It could be possible , that there are some index writes in WAL which are not

[jira] [Updated] (PHOENIX-2915) Dropping of Index can still leave some non-replayed writes in WAL

[ https://issues.apache.org/jira/browse/PHOENIX-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-2915: --- Description: It could be possible , that there are some index writes in WAL which are not

[jira] [Commented] (PHOENIX-2886) Union ALL with Char column not present in the table in Query 1 but in Query 2 throw exception

[ https://issues.apache.org/jira/browse/PHOENIX-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299621#comment-15299621 ] Sergey Soldatov commented on PHOENIX-2886: -- [~ayingshu] As I mentioned before it will require

[jira] [Commented] (PHOENIX-2886) Union ALL with Char column not present in the table in Query 1 but in Query 2 throw exception

[ https://issues.apache.org/jira/browse/PHOENIX-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299615#comment-15299615 ] Alicia Ying Shu commented on PHOENIX-2886: -- [~sergey.soldatov] Noticed the different lengths

[jira] [Issue Comment Deleted] (PHOENIX-2886) Union ALL with Char column not present in the table in Query 1 but in Query 2 throw exception

[ https://issues.apache.org/jira/browse/PHOENIX-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alicia Ying Shu updated PHOENIX-2886: - Comment: was deleted (was: [~sergey.soldatov] I noticed the different lengths for the

[jira] [Commented] (PHOENIX-2886) Union ALL with Char column not present in the table in Query 1 but in Query 2 throw exception

[ https://issues.apache.org/jira/browse/PHOENIX-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299596#comment-15299596 ] Alicia Ying Shu commented on PHOENIX-2886: -- [~sergey.soldatov] I noticed the different lengths