[
https://issues.apache.org/jira/browse/PHOENIX-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13895354#comment-13895354
]
James Violette commented on PHOENIX-11:
---------------------------------------
The syntax proposed works well.
A use case for a general select statement is a pig script that processes most
recent entries, or processes only errors. In that case, we could apply a
predicate to the select statement, have Phoenix use its efficient table
query/aggregation features, then allow only Pig to operate on pre-filtered data.
Is it easy to detect a query that updates data? This might work with pure
Phoenix keywords and aggregations. However, I suspect the presence of custom
keywords would make this difficult to assert in general. Perhaps we could have
a parameter that allows the user to specify their preference? By default the
loader would reject any Phoenix write key words.
How essential is it to reject write operations on load? I agree that selects
should be allowed and insert/upserts do not make sense on load. What about a
custom keyword that updates a status on load? That is not our use case at the
moment, but I have worked on systems where that was an essential database
feature. (Oracle allows a read from an index and a write to a status field
during the read, helping with parallel processing of bulk data).
> Create Pig Loader
> -----------------
>
> Key: PHOENIX-11
> URL: https://issues.apache.org/jira/browse/PHOENIX-11
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: maghamravikiran
>
> A Pig Storage function exists, so we can store to phoenix tables. What is
> needed is a Loader to go with the Storer.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
