[
https://issues.apache.org/jira/browse/PHOENIX-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14203556#comment-14203556
]
Kyle Buzsaki edited comment on PHOENIX-1425 at 11/8/14 7:33 PM:
----------------------------------------------------------------
Are you expecting 'insert' and 'update' to actually function like traditional
insert and update? If that's the case, the phoenix can't currently provide
that. There's no way to ensure that an insert is actually an insert or an
update is actually an update.
You would need some better form of handling concurrent modifications like
transactions, which are on the roadmap.
If all you want is a to make 'insert' and 'update' aliases for upsert, that
would be doable but it would likely be very confusing to new users.
was (Author: kbuzsaki):
Are you expecting 'insert' and 'update' to actually function like traditional
insert and update? If that's the case, the phoenix can't currently provide
that. There's no way to ensure that an insert is actually an insert or an
update is actually an update.
You would need some better form of handling concurrent modifications like
transactions, which are on the roadmap.
> Support of "select" and "insert" in jdbc. ORM tool support
> ----------------------------------------------------------
>
> Key: PHOENIX-1425
> URL: https://issues.apache.org/jira/browse/PHOENIX-1425
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Nickel Kosmos
> Priority: Trivial
>
> The idea is to support existing orm tools like hibernate. If you can add a
> replace statement, which replace "insert" or "update" with "upsert" in
> executequery(). Than it's much easier to write an dialect for this tools.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
