It sounds like you are scanning rather than getting rows based on a known
row id. Am I wrong?
One thing I am currently trying is to have indexed columns and "hot"
content in one column family and let "cold" content in another family. It
speed up scanning the table when you need to
Le mer. 1 juil.
Hi,
I want to perform :
SELECT * FROM "table" where "family"."column1" = 'value'
Running an EXPLAIN on this request before creating an index on a column
gives :
CLIENT PARALLEL 1-WAY FULL SCAN OVER table
SERVER FILTER BY family.column1 = 'value'
Looks OK.
Then I simply :
CREATE INDEX "table_I
Hi,
I got an existing HBase table, so I mapped to phoenix using a *view*. I can
select, create index, so I am happy.
Now I want to add a row (I assume it is not compulsory to have all column
values defined - would be boring otherwise with numerous columns):
upsert into "table" ("family1"."column
LE statement on a
re-generated hbase table fails for another reason (timeout).
Le mer. 1 juil. 2015 à 16:04, Martin Pernollet a
écrit :
> Hi,
>
> I got an existing HBase table, so I mapped to phoenix using a *view*. I
> can select, create index, so I am happy.
>
> Now I want
LIKE '/jquery%' |
>
> | DYNAMIC SERVER FILTER BY ("LOG.TS", "LOG.F", "LOG.R") IN
> (($707.$709, $707.$710, $707.$711)) |
>
>
>
>
>
> *From:* Martin Pernollet [mailto:mpernol...@octo.com]
> *Sent:* Wednesday, July 01, 2015 6:06 AM
rts
* Zookeeper informing on opened regions
* PostOpenDeployTasks
thanks in advance for your suggestions.
Le mer. 1 juil. 2015 à 17:09, Martin Pernollet a
écrit :
> I seems
> - CREATE TABLE returns the error "Table already exists" if you earlier
> created and dropped a view for t
timeouts really high so it has time to complete.
> Thanks,
> James
>
> On Mon, Jul 6, 2015 at 7:43 AM, Martin Pernollet
> wrote:
>
>> Hi,
>>
>> (using phoenix 4.2.2 on HDP 2.2)
>>
>> I would like to map an existing table from phoenix. Once mapped, th
