Dear All,
While running below query to create a table I encountered an error. Is there
any list of tokens/keywords that we cannot use as column name in Phoenix?
CREATE TABLE TTEST (ACTIVE BIGINT PRIMARY KEY, AC VARCHAR);
Error Message:
Error: Error -1 (0) : Error while executing SQL "create
Josh,
Thank you for your reply. I will take a look at your suggestions.
Thanks,
Paul
Hi Paul,
Unfortunately out of the box the Spark integration doesn't support saving to
dynamic columns. It's worth filing a JIRA enhancement over, and if you're
interested in contributing a patch, here's the
On Wed, Jul 27, 2016 at 8:07 AM, Heather, James (ELS) <
james.heat...@elsevier.com> wrote:
> - select * from documents where profile_id = ? (multiple rows returned,
> doing a full scan) --- 5 sec
>
> See https://phoenix.apache.org/secondary_indexing.html#Index_Usage for
> when an inde
I believe what you're saying is correct, James. The SMALL hint is calling
scan.setSmall(true) on the scans for your query. There's some documentation
on this here: https://issues.apache.org/jira/browse/HBASE-9488, but I'm
having a hard time finding other documentation. Small scans prevent as many
R
On Tue, 2016-07-26 at 08:39 -0700, James Taylor wrote:
- if you're querying for a single row, use the serial and small hints like
this: /*+ SERIAL SMALL */
Quoting from the language reference:
Generally, if the query is a point lookup or returns data that is likely in a
single data block (64 KB
- select * from documents where profile_id = ? (multiple rows returned, doing a
full scan) --- 5 sec
See https://phoenix.apache.org/secondary_indexing.html#Index_Usage for when an
index is used/not used, but by default a global index won't be used if not all
columns are contained i
Hi Paul,
Unfortunately out of the box the Spark integration doesn't support saving
to dynamic columns. It's worth filing a JIRA enhancement over, and if
you're interested in contributing a patch, here's the following spots I
think would need enhancing:
The saving code derives the column names to
