asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Hillery (JIRA)" <>
Subject [jira] [Commented] (ASTERIXDB-1150) ADM parser should accept AQL-style values
Date Thu, 22 Oct 2015 20:10:27 GMT


Chris Hillery commented on ASTERIXDB-1150:

Omitting the type suffixes altogether doesn't feel like the right solution to me. ADM (the
data model) distinguishes those types, so ADM (the serialized form) should at least have the
ability to do the same. Implied coercion is insufficiently precise, and doesn't work with
open fields as you say.

I don't think fixing the ADM parser would be hard. Another solution/work-around would be to
have the ADM serializer output eg. int32("55") instead of 55i32, which I believe the ADM parser
can support already. That'd be a little weird, though, and possibly less efficient if the
parser needed to construct a string object first and then convert that to an integer. The
only real benefit to that solution is that I know exactly how to do it in about 10 minutes.

> ADM parser should accept AQL-style values
> -----------------------------------------
>                 Key: ASTERIXDB-1150
>                 URL:
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: AsterixDB, Data Formats
>            Reporter: Chris Hillery
>            Assignee: Chris Hillery
>            Priority: Critical
> The AQL parser has several forms for representing values, but not all of them are parseable
by the ADM parser. In particular, length-specific integer types such as 15i8 cannot be loaded
into a dataset.
> This is particularly bad as the ADM serializer produces these style of values, meaning
ADM is not round-trippable.

This message was sent by Atlassian JIRA

View raw message