@Ashutosh
Did you solve this? I think i have similar issue with Phoenix
4.7.0/Hbase.1.1
I tried with phoenix-core-4.7.0...jar and it worked but not supporting JOIN
(
http://stackoverflow.com/questions/30730643/phoenix-join-operation-not-working-with-hbase)
and then I replaced it with phoenix-serv
Now that I see the VIEW solution written down, I think I tried something
similar (but *after* all UPSERTS, not *during* like you showed here.). I
tried to create a view consisting of the dynamic field names because I
hated the extra typing of specifying the field name and type after the
table name
Sure, Steve. Let's say you have a base table you define for your JSON
object like this:
-- Create sequence that doles out IDs when a new JSON type
-- is processed
CREATE SEQUENCE JSON_ID_SEQ;
-- Create base table for JSON
CREATE TABLE json (json_id BIGINT PRIMARY KEY,
created_date DATE
ra
James, I don't understand how to use IF NOT EXISTS to track the dynamic
columns. Could you elaborate? Thanks!
On Fri, Jun 3, 2016 at 10:36 AM, James Taylor
wrote:
> That's pretty slick, Steve. Another variant along the same lines would be
> to create/alter a view over a base table where you us
That's pretty slick, Steve. Another variant along the same lines would be
to create/alter a view over a base table where you use the IF NOT EXISTS.
In this way, you let Phoenix track the dynamic columns for you. We have a
new feature in 4.8 for declaring a table as an APPEND_ONLY_SCHEMA and we'll
m
I have a similar situation. I have records with varying fields that I
wanted to access individually and also as a group.
My actual records are JSON objects, so they look like like this:
{"field1": value1, "field2": value2, …}
To make matter harder, the fields are also varying types: ints, string
