Mailing-List: contact notifications-help@asterixdb.incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: dev@asterixdb.incubator.apache.org
Date: Fri, 18 Sep 2015 20:48:04 +0000 (UTC)
From: "Ian Maxon (JIRA)" <jira@apache.org>
To: notifications@asterixdb.incubator.apache.org
Message-ID: <JIRA.12888644.1442603224000.16269.1442609284844@Atlassian.JIRA>
In-Reply-To: <JIRA.12888644.1442603224000@Atlassian.JIRA>
References: <JIRA.12888644.1442603224000@Atlassian.JIRA>
 <JIRA.12888644.1442603224944@arcas>
Subject: [jira] [Commented] (ASTERIXDB-1102) Add a TEXT-like data type to
 enable storing the string longer than 64K
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ian Maxon commented on ASTERIXDB-1102:
--------------------------------------

We just use a default type for the literal AFAIK. For example, once upon a time you would say something like {"foo":42} and that'd be an int32, but it's an int64 now. There's ways to express the fact that a literal should be of a certain type, like 42i32 vs 42i64, but of course that'd be specific to ADM and not applicable to JSON. That's kind of why I couldn't imagine a totally clean solution to this if there's some real performance difference between string and text. If text turns out to just be like string with a wider length field though, it might not even make sense to keep the old format around as something user visible, just as long as we can read it in existing datasets. 


> Add a TEXT-like data type to enable storing the string longer than 64K
> ----------------------------------------------------------------------
>
>                 Key: ASTERIXDB-1102
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1102
>             Project: Apache AsterixDB
>          Issue Type: Improvement
>          Components: Data Model
>            Reporter: Jianfeng Jia
>            Assignee: Jianfeng Jia
>
> The current "String" type can't handle the string longer than 64K. The first reason is that we are using java DataOutputStream to serialize it. It stores the length using two bytes. However, it should serve the basic requirement for "string" type.
> We need a special TEXT-like datatype to deal with long strings. And probably add some search-related functionalities.


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