[jira] [Created] (PHOENIX-3362) Security - Add a context token to every query

2016-10-07 Thread L Martins (JIRA)
L Martins created PHOENIX-3362: -- Summary: Security - Add a context token to every query Key: PHOENIX-3362 URL: https://issues.apache.org/jira/browse/PHOENIX-3362 Project: Phoenix Issue Type:

Re: Multitenancy supported in phoenix-spark integration ?

2016-10-07 Thread Josh Mahonin
Hi Nico, To elaborate a little bit, there are two options for interfacing with Phoenix from Spark. Either using Spark's built-in JDBC integration, which uses the regular Phoenix JDBC driver, or by using the phoenix-spark integration, which leverages Phoenix's MapReduce support. If you are able to

[jira] [Commented] (PHOENIX-3363) Join-related IT had problematic usage of generating new table names

2016-10-07 Thread Maryann Xue (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556189#comment-15556189 ] Maryann Xue commented on PHOENIX-3363: -- Yes, [~jamestaylor], I know how this works. The map is for

Re: Multitenancy supported in phoenix-spark integration ?

2016-10-07 Thread Nico Pappagianis
Hmm, so I can query multi-tenant tables under a certain tenantId just fine. But when I create a multi-tenant view I am getting a table undefined error. This is because I am not actually connecting as the tenant (I realize not the predicate doesn't actually connect you as the tenant). It appears

Re: Multitenancy supported in phoenix-spark integration ?

2016-10-07 Thread Nico Pappagianis
Thanks Josh, The above works for multi-tenant tables that I have created for testing but I'm still running into issues with multi-tenant tables created elsewhere. I'll try to track down the DDL used to create the tables I'm having problems with - maybe that will illuminate some more things.

[jira] [Issue Comment Deleted] (PHOENIX-3363) Join-related IT had problematic usage of generating new table names

2016-10-07 Thread Maryann Xue (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated PHOENIX-3363: - Comment: was deleted (was: Yes, [~jamestaylor], I know how this works. The map is for locating

[jira] [Commented] (PHOENIX-3363) Join-related IT had problematic usage of generating new table names

2016-10-07 Thread Maryann Xue (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556195#comment-15556195 ] Maryann Xue commented on PHOENIX-3363: -- Sorry, [~jamestaylor], I was wrong. I'll find out why this

[jira] [Commented] (PHOENIX-2679) Implement column family schema structure in Calcite-Phoenix

2016-10-07 Thread Julian Hyde (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1643#comment-1643 ] Julian Hyde commented on PHOENIX-2679: -- [~jamestaylor], I think [~maryannxue] has found a good

Re: Multitenancy supported in phoenix-spark integration ?

2016-10-07 Thread James Taylor
Not sure if the phoenix-spark integration propagates connection properties, but an alternate way of specifying the tenant ID is through that mechanism (which would workaround the URL building issue). On Fri, Oct 7, 2016 at 10:06 AM, Nico Pappagianis < nico.pappagia...@salesforce.com> wrote: > Hi

[jira] [Commented] (PHOENIX-2679) Implement column family schema structure in Calcite-Phoenix

2016-10-07 Thread Julian Hyde (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1700#comment-1700 ] Julian Hyde commented on PHOENIX-2679: -- We're making sure that the hard stuff is in Calcite - in

[jira] [Commented] (PHOENIX-3353) Paged Queries: use of LIMIT + OFFSET with ORDER BY

2016-10-07 Thread Jasper van Ams (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1269#comment-1269 ] Jasper van Ams commented on PHOENIX-3353: - Important addition, given that: BAR is not a primary

Re: Multitenancy supported in phoenix-spark integration ?

2016-10-07 Thread Josh Mahonin
Hi Nico, Judging by that snippet above, it looks like you're actually using Spark's native JDBC integration though the regular Phoenix driver to create your source dataframe, not the spark-phoenix integration at all [1]. If that's sufficient for you, I suspect you can also use the DataFrame JDBC

[jira] [Commented] (PHOENIX-2679) Implement column family schema structure in Calcite-Phoenix

2016-10-07 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1674#comment-1674 ] James Taylor commented on PHOENIX-2679: --- Ok, thanks for taking a look. Overall, I'm hoping we can

Re: Multitenancy supported in phoenix-spark integration ?

2016-10-07 Thread Nico Pappagianis
Hi James, At first I thought it was the dataframe vs rdd implementations but looking closer my bet is the way spark connects to phoenix. When reading via SqlContext I pass in "url" -> "jdbc:phoenix:zkHost1, zkHost2, zkHost3:zkPort;TenantId=123456789" and it connects as the tenant. However

[jira] [Commented] (PHOENIX-3342) ORDER BY and LIMIT+OFFSET doesnt work on second column from compound key

2016-10-07 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1413#comment-1413 ] James Taylor commented on PHOENIX-3342: --- [~an...@apache.org]? > ORDER BY and LIMIT+OFFSET doesnt

[jira] [Updated] (PHOENIX-3342) ORDER BY and LIMIT+OFFSET doesnt work on second column from compound key

2016-10-07 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3342: -- Fix Version/s: 4.8.2 4.9.0 > ORDER BY and LIMIT+OFFSET doesnt work on

[jira] [Updated] (PHOENIX-3353) Paged Queries: use of LIMIT + OFFSET with ORDER BY

2016-10-07 Thread Jasper van Ams (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jasper van Ams updated PHOENIX-3353: Description: As per documentation (https://phoenix.apache.org/paged.html) SELECT * FROM

Re: Multitenancy supported in phoenix-spark integration ?

2016-10-07 Thread James Taylor
Hi Nico, You mentioned offline that it seems to be working for data frames, but not RDDs. Can you elaborate on that? Have you confirmed whether the TenantId connection property is being propagated down to the Phoenix connection opened for the Spark integration? Thanks, James On Thu, Oct 6, 2016

[jira] [Assigned] (PHOENIX-3359) Update JDBC urls to match connection type

2016-10-07 Thread Eric Lomore (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lomore reassigned PHOENIX-3359: Assignee: Eric Lomore > Update JDBC urls to match connection type >

[jira] [Commented] (PHOENIX-476) Support declaration of DEFAULT in CREATE statement

2016-10-07 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1482#comment-1482 ] James Taylor commented on PHOENIX-476: -- Any progress on this, [~kliew]? > Support declaration of

Re: Multitenancy supported in phoenix-spark integration ?

2016-10-07 Thread Nico Pappagianis
Thanks James, I am able to read from the tenant-specific view using the SQLContext.read function, which gives a DataFrameReader to work with. However the SQLContext class doesn't appear to have any functionality for writing. SQLContext has, so far, been the only way I've been able to read a

[jira] [Resolved] (PHOENIX-3363) Join-related IT had problematic usage of generating new table names

2016-10-07 Thread Maryann Xue (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue resolved PHOENIX-3363. -- Resolution: Fixed > Join-related IT had problematic usage of generating new table names >

[jira] [Resolved] (PHOENIX-3364) ConcurrentModificationException from PhoenixSchema in adding secondary indexes

2016-10-07 Thread Maryann Xue (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue resolved PHOENIX-3364. -- Resolution: Fixed > ConcurrentModificationException from PhoenixSchema in adding secondary

[jira] [Commented] (PHOENIX-3363) Join-related IT had problematic usage of generating new table names

2016-10-07 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556096#comment-15556096 ] Hudson commented on PHOENIX-3363: - FAILURE: Integrated in Jenkins build Phoenix-master #1433 (See

[jira] [Commented] (PHOENIX-3363) Join-related IT had problematic usage of generating new table names

2016-10-07 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1937#comment-1937 ] James Taylor commented on PHOENIX-3363: --- Because of the way the tests are designed, we have a

Re: Multitenancy supported in phoenix-spark integration ?

2016-10-07 Thread Nico Pappagianis
Hi Josh just saw your post. Let me take a look at that stack overflow post you linked. Could you elaborate on how you pass TenantID manually? Thanks On Fri, Oct 7, 2016 at 11:27 AM, Nico Pappagianis < nico.pappagia...@salesforce.com> wrote: > Thanks James, > > I am able to read from the

[jira] [Created] (PHOENIX-3363) Join-related IT had problematic usage of generating new table names

2016-10-07 Thread Maryann Xue (JIRA)
Maryann Xue created PHOENIX-3363: Summary: Join-related IT had problematic usage of generating new table names Key: PHOENIX-3363 URL: https://issues.apache.org/jira/browse/PHOENIX-3363 Project:

[jira] [Updated] (PHOENIX-3363) Join-related IT had problematic usage of generating new table names

2016-10-07 Thread Maryann Xue (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated PHOENIX-3363: - Description: If there are multiple references of the same table, we should only call method

[jira] [Updated] (PHOENIX-2675) Allow stats to be configured on a table-by-table basis

2016-10-07 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2675: -- Attachment: PHOENIX-2675.patch Please review, [~samarthjain]. This goes together with

[jira] [Updated] (PHOENIX-3361) Collect stats correctly for local indexes

2016-10-07 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3361: -- Summary: Collect stats correctly for local indexes (was: Collect stats correct for local

[jira] [Commented] (PHOENIX-2675) Allow stats to be configured on a table-by-table basis

2016-10-07 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556805#comment-15556805 ] Hadoop QA commented on PHOENIX-2675: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (PHOENIX-3361) Collect stats correctly for local indexes

2016-10-07 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3361: -- Attachment: PHOENIX-3361.patch Please review, [~samarthjain]. This patch also includes

[jira] [Commented] (PHOENIX-476) Support declaration of DEFAULT in CREATE statement

2016-10-07 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556975#comment-15556975 ] James Taylor commented on PHOENIX-476: -- Thanks for the update, but I really need to see an updated

[jira] [Commented] (PHOENIX-3361) Collect stats correctly for local indexes

2016-10-07 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556815#comment-15556815 ] Hadoop QA commented on PHOENIX-3361: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (PHOENIX-3174) Make minor upgrade a manual step

2016-10-07 Thread Ankit Singhal (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15554868#comment-15554868 ] Ankit Singhal commented on PHOENIX-3174: [~samarthjain], couple of things found while testing

[jira] [Commented] (PHOENIX-3296) ArrayConstructor expression does not serialize arrays with leading nulls correctly.

2016-10-07 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15554579#comment-15554579 ] Hudson commented on PHOENIX-3296: - SUCCESS: Integrated in Jenkins build Phoenix-master #1432 (See

[jira] [Commented] (PHOENIX-3296) ArrayConstructor expression does not serialize arrays with leading nulls correctly.

2016-10-07 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15554556#comment-15554556 ] Hudson commented on PHOENIX-3296: - FAILURE: Integrated in Jenkins build Phoenix-4.8-HBase-1.2 #34 (See

[jira] [Assigned] (PHOENIX-3361) Collect stats correctly for local indexes

2016-10-07 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-3361: - Assignee: James Taylor > Collect stats correctly for local indexes >

[jira] [Updated] (PHOENIX-3361) Collect stats correctly for local indexes

2016-10-07 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3361: -- Description: Stats are not being correctly collected for local indexes and tables with local

[jira] [Commented] (PHOENIX-476) Support declaration of DEFAULT in CREATE statement

2016-10-07 Thread Kevin Liew (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556926#comment-15556926 ] Kevin Liew commented on PHOENIX-476: Hi [~jamestaylor], sorry for the delay. I've been working on

[jira] [Commented] (PHOENIX-3357) Issue with column re-ordering in column family support for Calcite-Phoenix

2016-10-07 Thread Maryann Xue (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556172#comment-15556172 ] Maryann Xue commented on PHOENIX-3357: -- [~jamestaylor] and [~julianhyde], looks like we need some

[jira] [Commented] (PHOENIX-3363) Join-related IT had problematic usage of generating new table names

2016-10-07 Thread Maryann Xue (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556254#comment-15556254 ] Maryann Xue commented on PHOENIX-3363: -- Ok, just realized that Calcite does not allow referring a

[jira] [Updated] (PHOENIX-476) Support declaration of DEFAULT in CREATE statement

2016-10-07 Thread Kevin Liew (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Liew updated PHOENIX-476: --- Attachment: PHOENIX-476.4.patch I attached the latest patch. For clarity I should have said it