You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/01/11 17:21:40 UTC

[jira] [Commented] (ASTERIXDB-1252) Problems with Autogenerated Key

    [ https://issues.apache.org/jira/browse/ASTERIXDB-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092205#comment-15092205 ] 

ASF subversion and git services commented on ASTERIXDB-1252:
------------------------------------------------------------

Commit 4053f390af30d7d8cbf906fd874291a28a1b1c0b in incubator-asterixdb's branch refs/heads/master from [~heriram]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-asterixdb.git;h=4053f39 ]

ASTERIXDB-1187, ASTERIXDB-1162 and ASTERIXDB-1252 fixes, plus new internal functions

This change contains the following updates and fixes:
- New deep-equality function which also handles numeric equality,
e.g., [2.0, 2, 1.0] == [2, 2, 1].
- New internal functions for record manipulation, including add and remove fields from records
- Fixes for ASTERIXDB-1187: The RecordMergeDescriptor does not fully support
open record merge. Merging records with open fields results in "NullPointerException".
- Fixes to address issue ASTERIXDB-1162: dealing with closed or partly closed record
added to an open record field.
- Fixes issue ASTERIXDB-1252: Problems with Autogenerated Key

Change-Id: I3621ebdd71c7cd91b50d77a972ad863cea7fcbc2
Reviewed-on: https://asterix-gerrit.ics.uci.edu/298
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: Till Westmann <ti...@apache.org>


> Problems with Autogenerated Key
> -------------------------------
>
>                 Key: ASTERIXDB-1252
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1252
>             Project: Apache AsterixDB
>          Issue Type: Bug
>            Reporter: Steven Jacobs
>
> There seems to be some kind of bug with record merge and auto generated keys. The following query fails. If I remove either subscriptionId or deliveryTime from the schema and insert, things work fine.
> drop dataverse channels if exists;
> create dataverse channels;
> use dataverse channels;
> create type TypeA as closed {
> "resultId":uuid,
> "subscriptionId":uuid,
> "deliveryTime":datetime
> }
> create dataset nearbyTweetChannelResults(TypeA) primary key resultId autogenerated;
> insert into dataset nearbyTweetChannelResults(
> {"subscriptionId":uuid("d0b6fac0-3903-43dc-8ef6-7b0923ffc759"), 
> "deliveryTime":datetime("2011-08-25T10:10:00.000Z")}
> );



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)