[jira] [Updated] (PHOENIX-1263) Only cache guideposts on physical PTable

[ https://issues.apache.org/jira/browse/PHOENIX-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated PHOENIX-1263: Attachment: Phoenix-1263_6.patch Latest patch addressing all the review co

[jira] [Updated] (PHOENIX-1251) Salted queries with range scan become full table scans

[ https://issues.apache.org/jira/browse/PHOENIX-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-1251: -- Attachment: PHOENIX-1251.patch WIP patch > Salted queries with range scan become full table s

[jira] [Commented] (PHOENIX-1263) Only cache guideposts on physical PTable

[ https://issues.apache.org/jira/browse/PHOENIX-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152771#comment-14152771 ] ramkrishna.s.vasudevan commented on PHOENIX-1263: - [~jeffreyz] Thanks fo

[jira] [Commented] (PHOENIX-1249) Support local immutable index

[ https://issues.apache.org/jira/browse/PHOENIX-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152722#comment-14152722 ] Hudson commented on PHOENIX-1249: - FAILURE: Integrated in Phoenix | Master | Hadoop1 #39

[jira] [Commented] (PHOENIX-914) Native HBase timestamp support to optimize date range queries in Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152678#comment-14152678 ] Jeffrey Zhong commented on PHOENIX-914: --- {quote} How will the user know the relatio

[jira] [Commented] (PHOENIX-914) Native HBase timestamp support to optimize date range queries in Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152646#comment-14152646 ] James Taylor commented on PHOENIX-914: -- How will the user know the relationship betw

[jira] [Commented] (PHOENIX-914) Native HBase timestamp support to optimize date range queries in Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152628#comment-14152628 ] Jeffrey Zhong commented on PHOENIX-914: --- {quote} >From what I've seen of these Phoe

[jira] [Comment Edited] (PHOENIX-1297) Adding utility methods to get primary key information from the optimized query plan

[ https://issues.apache.org/jira/browse/PHOENIX-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152568#comment-14152568 ] Samarth Jain edited comment on PHOENIX-1297 at 9/30/14 12:29 AM: -

[jira] [Commented] (PHOENIX-914) Native HBase timestamp support to optimize date range queries in Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152589#comment-14152589 ] James Taylor commented on PHOENIX-914: -- For the same row, there may be different tim

[jira] [Updated] (PHOENIX-1297) Adding utility methods to get primary key information from the optimized query plan

[ https://issues.apache.org/jira/browse/PHOENIX-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-1297: -- Attachment: PHOENIX-1297.patch [~jamestaylor] - attached is the patch for master branch. It co

[jira] [Commented] (PHOENIX-914) Native HBase timestamp support to optimize date range queries in Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152545#comment-14152545 ] Jeffrey Zhong commented on PHOENIX-914: --- The hbase row key timestamp are always the

[jira] [Created] (PHOENIX-1304) Customize "full scan" behavior

Lars Hofhansl created PHOENIX-1304: -- Summary: Customize "full scan" behavior Key: PHOENIX-1304 URL: https://issues.apache.org/jira/browse/PHOENIX-1304 Project: Phoenix Issue Type: Improvemen

[jira] [Commented] (PHOENIX-914) Native HBase timestamp support to optimize date range queries in Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152492#comment-14152492 ] James Taylor commented on PHOENIX-914: -- For this proposal, it's proposed to be a rea

[jira] [Commented] (PHOENIX-914) Native HBase timestamp support to optimize date range queries in Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152475#comment-14152475 ] Jeffrey Zhong commented on PHOENIX-914: --- Thanks for the clarifications! If we only

[jira] [Commented] (PHOENIX-914) Native HBase timestamp support to optimize date range queries in Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152368#comment-14152368 ] James Taylor commented on PHOENIX-914: -- [~jeffreyz] - the proposal here isn't to dir

[jira] [Commented] (PHOENIX-1263) Only cache guideposts on physical PTable

[ https://issues.apache.org/jira/browse/PHOENIX-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152240#comment-14152240 ] Jeffrey Zhong commented on PHOENIX-1263: If you have a hbase already running on

[jira] [Commented] (PHOENIX-914) Native HBase timestamp support to optimize date range queries in Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152195#comment-14152195 ] Jeffrey Zhong commented on PHOENIX-914: --- One problem to directly expose HBase row k

[jira] [Commented] (PHOENIX-1293) By default we should not disable wal for immutable indexes otherwise we end up in data loss on RS failure

[ https://issues.apache.org/jira/browse/PHOENIX-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152151#comment-14152151 ] rajeshbabu commented on PHOENIX-1293: - Same problem coming randomly in previous buil

[jira] [Created] (PHOENIX-1303) Possible NPE in StatisticCollector#stop

rajeshbabu created PHOENIX-1303: --- Summary: Possible NPE in StatisticCollector#stop Key: PHOENIX-1303 URL: https://issues.apache.org/jira/browse/PHOENIX-1303 Project: Phoenix Issue Type: Bug

[jira] [Commented] (PHOENIX-1293) By default we should not disable wal for immutable indexes otherwise we end up in data loss on RS failure

[ https://issues.apache.org/jira/browse/PHOENIX-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152133#comment-14152133 ] rajeshbabu commented on PHOENIX-1293: - I have observed possible NPE while closing SY

[jira] [Created] (PHOENIX-1302) Query against tenant specific view should use index

Samarth Jain created PHOENIX-1302: - Summary: Query against tenant specific view should use index Key: PHOENIX-1302 URL: https://issues.apache.org/jira/browse/PHOENIX-1302 Project: Phoenix Iss

[jira] [Created] (PHOENIX-1301) PTable.getParentTableName() should include the schema name if present

Samarth Jain created PHOENIX-1301: - Summary: PTable.getParentTableName() should include the schema name if present Key: PHOENIX-1301 URL: https://issues.apache.org/jira/browse/PHOENIX-1301 Project: Ph

[jira] [Commented] (PHOENIX-1293) By default we should not disable wal for immutable indexes otherwise we end up in data loss on RS failure

[ https://issues.apache.org/jira/browse/PHOENIX-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152065#comment-14152065 ] James Taylor commented on PHOENIX-1293: --- Looks like the 3.0 branch failed - might

[jira] [Resolved] (PHOENIX-1293) By default we should not disable wal for immutable indexes otherwise we end up in data loss on RS failure

[ https://issues.apache.org/jira/browse/PHOENIX-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rajeshbabu resolved PHOENIX-1293. - Resolution: Fixed Pushed to 3.0,4.0 and master branches. Thanks for review [~jamestaylor]. > By

[jira] [Commented] (PHOENIX-1264) Add StatisticsCollector to existing tables on first connection to cluster

[ https://issues.apache.org/jira/browse/PHOENIX-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152032#comment-14152032 ] James Taylor commented on PHOENIX-1264: --- Looks good, [~ramkrishna]. One minor chan

[jira] [Commented] (PHOENIX-1263) Only cache guideposts on physical PTable

[ https://issues.apache.org/jira/browse/PHOENIX-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152020#comment-14152020 ] James Taylor commented on PHOENIX-1263: --- I've never run Windows, but [~jeffreyz] h

[jira] [Commented] (PHOENIX-1273) Phoenix should provide ILIKE keyword

[ https://issues.apache.org/jira/browse/PHOENIX-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151882#comment-14151882 ] James Taylor commented on PHOENIX-1273: --- This new keyword will be available once w

[jira] [Created] (PHOENIX-1300) Allow sub-queries to choose different execution path other than hash-join

Maryann Xue created PHOENIX-1300: Summary: Allow sub-queries to choose different execution path other than hash-join Key: PHOENIX-1300 URL: https://issues.apache.org/jira/browse/PHOENIX-1300 Project:

[jira] [Updated] (PHOENIX-1299) Optimize ANY/SOME/ALL sub-queries

[ https://issues.apache.org/jira/browse/PHOENIX-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated PHOENIX-1299: - Issue Type: Improvement (was: Bug) > Optimize ANY/SOME/ALL sub-queries > --

[jira] [Created] (PHOENIX-1299) Optimize ANY/SOME/ALL sub-queries

Maryann Xue created PHOENIX-1299: Summary: Optimize ANY/SOME/ALL sub-queries Key: PHOENIX-1299 URL: https://issues.apache.org/jira/browse/PHOENIX-1299 Project: Phoenix Issue Type: Bug Aff

Re: Hbase namespaces

I thought you wanted to have a single physical Phoenix table (backed by a single HBase table) be shared for multiple purposes. If so, views are a good way to do that. You create a regular table in Phoenix and then define views on top of that table based on your requirements. Views share the parent

[jira] [Commented] (PHOENIX-1273) Phoenix should provide ILIKE keyword

[ https://issues.apache.org/jira/browse/PHOENIX-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151661#comment-14151661 ] Jean-Marc Spaggiari commented on PHOENIX-1273: -- Oh, cool! That's a good new

[jira] [Updated] (PHOENIX-1264) Add StatisticsCollector to existing tables on first connection to cluster

[ https://issues.apache.org/jira/browse/PHOENIX-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated PHOENIX-1264: Attachment: Phoenix-1264_3.0_3.patch Attaching a patch for 3.0 that combin

[jira] [Commented] (PHOENIX-1296) Scan entire region when tenant-specific table is analyzed

[ https://issues.apache.org/jira/browse/PHOENIX-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151520#comment-14151520 ] ramkrishna.s.vasudevan commented on PHOENIX-1296: - I think this is not t

Re: Hbase namespaces

Hello Eli Views were one way I was thinking about, but actually what mean is creating and using an Hbase table like "mydb:mytable" so either creatng it directly through Phoenix or creating a view on top of the hbase table to access my phoenix semantics. Hope this makes sense On Fri, Sep 26, 2014

[jira] [Commented] (PHOENIX-1293) By default we should not disable wal for immutable indexes otherwise we end up in data loss on RS failure

[ https://issues.apache.org/jira/browse/PHOENIX-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151441#comment-14151441 ] Hudson commented on PHOENIX-1293: - FAILURE: Integrated in Phoenix | 3.0 | Hadoop1 #234 (

[jira] [Commented] (PHOENIX-1263) Only cache guideposts on physical PTable

[ https://issues.apache.org/jira/browse/PHOENIX-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151426#comment-14151426 ] ramkrishna.s.vasudevan commented on PHOENIX-1263: - Thanks for the feedba