Jan Van Besien created PHOENIX-7351:
---
Summary: unnecessary ERROR logging in RenewLeaseTask
Key: PHOENIX-7351
URL: https://issues.apache.org/jira/browse/PHOENIX-7351
Project: Phoenix
Issue
[
https://issues.apache.org/jira/browse/PHOENIX-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144288#comment-15144288
]
Jan Van Besien commented on PHOENIX-2680:
-
[~jamestaylor] - thanks for
[
https://issues.apache.org/jira/browse/PHOENIX-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Van Besien updated PHOENIX-2680:
Attachment: PHOENIX-2680.patch
Patch against master. Essentially I just removed the line
Jan Van Besien created PHOENIX-2680:
---
Summary: stats table timestamp incorrectly used as table timestamp
Key: PHOENIX-2680
URL: https://issues.apache.org/jira/browse/PHOENIX-2680
Project: Phoenix
[
https://issues.apache.org/jira/browse/PHOENIX-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Van Besien updated PHOENIX-2664:
Affects Version/s: 4.6.0
> Upgrade from 4.1.0 to 4.6.0 fa
[
https://issues.apache.org/jira/browse/PHOENIX-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Van Besien updated PHOENIX-2664:
Attachment: PHOENIX-2664.patch
Patch against master.
Apart from the UpgradeIT I couldn&#
Jan Van Besien created PHOENIX-2664:
---
Summary: Upgrade from 4.1.0 to 4.6.0 fails
Key: PHOENIX-2664
URL: https://issues.apache.org/jira/browse/PHOENIX-2664
Project: Phoenix
Issue Type: Bug
Hi,
We are working on a calcite/avatica based "thin" JDBC driver very
similar to what Phoenix has done with for its QueryServer, and I am
looking for some feedback/options.
Avatica in its current state doesn't have an RPC call for "create
connection". As a consequence, connection properties (i.e.
On Fri, Jan 16, 2015 at 1:16 PM, Gabriel Reid wrote:
> Just taking a look at this as well -- I guess another way of putting
> it is that empty arrays don't (yet) exist in Phoenix (right?)
yes indeed.
> My guess would be that it's more the fact that empty arrays don't
> exist (if my assumption ab
On Fri, Jan 16, 2015 at 11:50 AM, Jan Van Besien wrote:
> I had a quick look at how arrays are serialized. The serialization
> format starts by writing out the length of the array
Upon closer inspection, it does this only if the baseType is a
variable length type. So a straightforward fix
Hi,
In the context of "store nulls", Phoenix seems to store empty arrays
and null arrays both as an empty byte array. We have a use case where
null means something different than empty.
I had a quick look at how arrays are serialized. The serialization
format starts by writing out the length of t
[
https://issues.apache.org/jira/browse/PHOENIX-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Van Besien updated PHOENIX-1587:
Attachment: unit-test-for-PHOENIX-1587.patch
Attached a patch with some unit tests for
I created PHOENIX-1587 and added a patch.
On Thu, Jan 15, 2015 at 10:39 AM, Jan Van Besien wrote:
> Hi,
>
> I think there is a bug in PArrayDataType, in the context of "store nulls".
>
> The first line of the createPhoenixArray method tackles the case where
> an emp
Jan Van Besien created PHOENIX-1587:
---
Summary: Error deserializing empty array (which represents null)
Key: PHOENIX-1587
URL: https://issues.apache.org/jira/browse/PHOENIX-1587
Project: Phoenix
[
https://issues.apache.org/jira/browse/PHOENIX-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Van Besien updated PHOENIX-1587:
Attachment: PHOENIX-1587.patch
patch for the issue on the master branch.
> Er
Hi,
I think there is a bug in PArrayDataType, in the context of "store nulls".
The first line of the createPhoenixArray method tackles the case where
an empty byte array is interpreted as null. However, I think the check
should be
if (bytes == null || length == 0)
rather than
if (bytes == null
[
https://issues.apache.org/jira/browse/PHOENIX-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Van Besien updated PHOENIX-1214:
Attachment: 0001-PHOENIX-1214-support-tenant-specific-initial-connect.patch
I looked into
[
https://issues.apache.org/jira/browse/PHOENIX-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14111897#comment-14111897
]
Jan Van Besien commented on PHOENIX-1204:
-
Perfect, no more confusion and
[
https://issues.apache.org/jira/browse/PHOENIX-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110395#comment-14110395
]
Jan Van Besien commented on PHOENIX-1204:
-
yes, this is certainl
Jan Van Besien created PHOENIX-1204:
---
Summary: Unclear multi tenancy docs
Key: PHOENIX-1204
URL: https://issues.apache.org/jira/browse/PHOENIX-1204
Project: Phoenix
Issue Type: Improvement
20 matches
Mail list logo
