[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15645719#comment-15645719
]
Gary Horen commented on PHOENIX-6:
--
in the near term this will probably be mostly single rows / commit. As
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15613510#comment-15613510
]
Hudson commented on PHOENIX-6:
--
SUCCESS: Integrated in Jenkins build Phoenix-master #1455 (See
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15613167#comment-15613167
]
Hadoop QA commented on PHOENIX-6:
-
{color:red}-1 overall{color}. Here are the results of testing the
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15613164#comment-15613164
]
Samarth Jain commented on PHOENIX-6:
+1, this is a great addition, [~jamestaylor]!
> Support ON
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15613077#comment-15613077
]
James Taylor commented on PHOENIX-6:
bq. How about a covered column test case for local indexes too?
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15612995#comment-15612995
]
Samarth Jain commented on PHOENIX-6:
Thanks for the explanation, makes sense.
bq. This is already
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15612838#comment-15612838
]
James Taylor commented on PHOENIX-6:
bq. How about a couple more test cases where the expression to be
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15612798#comment-15612798
]
Samarth Jain commented on PHOENIX-6:
Patch looks good, [~jamestaylor]. How about a couple more test
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15612601#comment-15612601
]
Samarth Jain commented on PHOENIX-6:
Couple of questions, [~jamestaylor], otherwise the patch looks
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15612583#comment-15612583
]
Samarth Jain commented on PHOENIX-6:
{code}
+// We cannot neither use the time stamp in the
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15610914#comment-15610914
]
Samarth Jain commented on PHOENIX-6:
[~jamestaylor] - is there any restriction on what kind of
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15610459#comment-15610459
]
Hadoop QA commented on PHOENIX-6:
-
{color:red}-1 overall{color}. Here are the results of testing the
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15607551#comment-15607551
]
Hadoop QA commented on PHOENIX-6:
-
{color:red}-1 overall{color}. Here are the results of testing the
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15607265#comment-15607265
]
James Taylor commented on PHOENIX-6:
[~gho...@salesforce.com] - Can you give us a bit of information on
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15606891#comment-15606891
]
Hadoop QA commented on PHOENIX-6:
-
{color:red}-1 overall{color}. Here are the results of testing the
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15606521#comment-15606521
]
Mujtaba Chohan commented on PHOENIX-6:
--
Sure [~jamestaylor]
> Support ON DUPLICATE KEY construct
>
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576237#comment-15576237
]
Cameron Hatfield commented on PHOENIX-6:
And in general, I agree with the heavyweightness of the
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576149#comment-15576149
]
Cameron Hatfield commented on PHOENIX-6:
It would work for me, though I'm not sure if it would be
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576121#comment-15576121
]
Cameron Hatfield commented on PHOENIX-6:
Here is what MSSQL does to handle not having to repeat the
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576102#comment-15576102
]
Cameron Hatfield commented on PHOENIX-6:
In general, the main use case I have is reducing RPC calls
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563263#comment-15563263
]
James Taylor commented on PHOENIX-6:
I'm exploring an alternate syntax (with equivalent functionality)
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15547135#comment-15547135
]
James Taylor commented on PHOENIX-6:
Would you mind filing a separate JIRA for your use case? If I
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15546874#comment-15546874
]
Cameron Hatfield commented on PHOENIX-6:
For the help with my use case question, not really, due to
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15546680#comment-15546680
]
James Taylor commented on PHOENIX-6:
With Phoenix, for non transactional tables, the updates to the
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15546605#comment-15546605
]
Cameron Hatfield commented on PHOENIX-6:
Ahh, I saw where I was getting confused. I thought that
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15546487#comment-15546487
]
James Taylor commented on PHOENIX-6:
Yes, agreed, [~cameron.hatfield]. If these two statements are in
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15546436#comment-15546436
]
Cameron Hatfield commented on PHOENIX-6:
Except, in the second case (two statements, same batch),
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15546218#comment-15546218
]
James Taylor commented on PHOENIX-6:
The UPSERT VALUES ... ON DUPLICATE KEY will be evaluated on the
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15543719#comment-15543719
]
Cameron Hatfield commented on PHOENIX-6:
And as a general note, though inefficent, when combined
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15543705#comment-15543705
]
Cameron Hatfield commented on PHOENIX-6:
At what point will the expressions be evaluated in the
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15531383#comment-15531383
]
James Taylor commented on PHOENIX-6:
bq. but incrementing a numeric column can use the optimized path,
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15531316#comment-15531316
]
Gary Horen commented on PHOENIX-6:
--
[~giacomotaylor]:
>>would thus require a read before write
For a
[
https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530929#comment-15530929
]
James Taylor commented on PHOENIX-6:
FYI, [~gho...@salesforce.com]
> Support ON DUPLICATE KEY
33 matches
Mail list logo