[
https://issues.apache.org/jira/browse/PHOENIX-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1223:
--
Summary: Support VARBINARY declaration anywhere in the PK constraint (was:
Support VARBINARY
[
https://issues.apache.org/jira/browse/PHOENIX-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1223:
--
Issue Type: Improvement (was: Bug)
> Support VARBINARY declaration anywhere in the PK
[
https://issues.apache.org/jira/browse/PHOENIX-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1223:
--
Description:
Since a VARBINARY can be any length with any bytes, we cannot know where it
[
https://issues.apache.org/jira/browse/PHOENIX-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1223:
--
Description:
Since a VARBINARY can be any length with any bytes, we cannot know where it
[
https://issues.apache.org/jira/browse/PHOENIX-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066902#comment-15066902
]
Hudson commented on PHOENIX-2503:
-
FAILURE: Integrated in Phoenix-master #1031 (See
[
https://issues.apache.org/jira/browse/PHOENIX-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067016#comment-15067016
]
maghamravikiran commented on PHOENIX-2540:
--
[~warwithin] A quick test against the 4.6.0 v
hi all:
I'm reading phoenix src code recently, and i found
PRowImpl.toRowMutations() always adds an empty column named '_0' for non-delete
upsert. Why?
I read the comment but i didn't quite understand it. Might someone give me
an example that illustates why an empty column is ALWAYS
Hi William,
The empty column is needed to ensure that a given column is available
for all rows.
As you may know, data is stored in HBase as KeyValues, meaning that
the full row key is stored for each column value. This also implies
that the row key is not stored at all unless there is at least
[
https://issues.apache.org/jira/browse/PHOENIX-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067536#comment-15067536
]
ramkrishna.s.vasudevan commented on PHOENIX-1312:
-
{code}
[ERROR] COMPILATION ERROR :
[
https://issues.apache.org/jira/browse/PHOENIX-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas D'Silva updated PHOENIX-2525:
Attachment: PHOENIX-2525.patch
[~jamestaylor]
Can you please review?
In addition to
[
https://issues.apache.org/jira/browse/PHOENIX-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067517#comment-15067517
]
YoungWoo Kim commented on PHOENIX-2540:
---
[~maghamraviki...@gmail.com], Thanks for investigating on
[
https://issues.apache.org/jira/browse/PHOENIX-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
YoungWoo Kim resolved PHOENIX-2540.
---
Resolution: Cannot Reproduce
> Same column twice in CREATE TABLE leads unusable state of
Hi Gabriel:
Now I think I understand why an empty column is necessary. I did the following
tests:
1. by HBASE native API: after I deleted the last attribute column of a
specified row, the whole row was deleted.
and this is exactly what you said 'the row key is not stored at all unless
[
https://issues.apache.org/jira/browse/PHOENIX-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067425#comment-15067425
]
YoungWoo Kim commented on PHOENIX-2481:
---
[~ndimiduk], Nice work! I have a comment for this
[
https://issues.apache.org/jira/browse/PHOENIX-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066180#comment-15066180
]
ramkrishna.s.vasudevan commented on PHOENIX-1312:
-
Pushed to master, 4.x-0.98 and
[
https://issues.apache.org/jira/browse/PHOENIX-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066234#comment-15066234
]
ramkrishna.s.vasudevan commented on PHOENIX-1312:
-
0.98 branch has a compilation issue.
Hi William,
Yes, all your tests there look correct, and it looks like you've got a
good understanding on the underlying principles of how scans are
working in Phoenix vs HBase.
About the use of "not null" constraints, you're correct about data
being written by non-Phoenix clients being an issue.
[
https://issues.apache.org/jira/browse/PHOENIX-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066360#comment-15066360
]
Hudson commented on PHOENIX-1312:
-
FAILURE: Integrated in Phoenix-master #1030 (See
[
https://issues.apache.org/jira/browse/PHOENIX-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor resolved PHOENIX-1940.
---
Resolution: Won't Fix
By implementing PHOENIX-1598, we won't need to do this as the
[
https://issues.apache.org/jira/browse/PHOENIX-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Mahonin resolved PHOENIX-2503.
---
Resolution: Fixed
Needs documentation update. Spark users must use new 'client-spark' JAR
[
https://issues.apache.org/jira/browse/PHOENIX-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066597#comment-15066597
]
Ankit Singhal commented on PHOENIX-1566:
[~jamestaylor], can we close this as duplicate of
[
https://issues.apache.org/jira/browse/PHOENIX-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Mahonin reassigned PHOENIX-2503:
-
Assignee: Josh Mahonin
> Multiple Java NoClass/Method Errors with Spark and Phoenix
>
22 matches
Mail list logo
