Hi ,
I am executing 2 join queries which give the same response.
Query 1: Nested join over 5 tables where . The query uses rowkey "like"
statement to narrow down to the filtered columns. This query in Phoenix sqlline
terminal takes 800millisecs to execute.
Query 2: Is a inner join over the same
+1 the table should exist in phoenix.
On Thu, Jul 20, 2017 at 5:25 AM, Josh Mahonin wrote:
> Hi Luqman,
>
> At present, the phoenix-spark integration relies on the schema having been
> already created.
>
> There has been some discussion of augmenting the supported Spark
> 'SaveMode's to include
Hi,
We have a CUSTOMER table created via phoenix with view on that table called
CUSTOMER_VIEW.
We have a ranger policy in place for the table.
User1 has permissions to create, read, write.
User2 has permission to read only.
For User1, we didn't encounter any error when querying with Limit.
Hi Luqman,
At present, the phoenix-spark integration relies on the schema having been
already created.
There has been some discussion of augmenting the supported Spark
'SaveMode's to include 'CREATE IF NOT EXISTS' logic.
https://issues.apache.org/jira/browse/PHOENIX-2745
https://issues.apache.or
Hi Siddharth
The problem that was described in PHOENIX-3196 (as well as in PHOENIX-930
and several others) is that we sent metadata updates for the table before
checking whether there is a problem with duplicated column names. I don't
think you hit the same problem if you are using alter tables. Co
