[
https://issues.apache.org/jira/browse/ASTERIXDB-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xikui Wang updated ASTERIXDB-1394:
----------------------------------
Description:
The TweetParser can only take dataset definition with specific order as follow:
{quote}
create type Tweet if not exists as open\{
id: string,
user: TwitterUser,
latitude:double,
longitude:double,
created_at:string,
message_text:string
\};
{quote}
Different order will cause type cast exception since the order is fixed in
code. Also the names of field and number is also fixed, no more or less.
Also Tweet cannot have extra field, and extra field will cause
ArrayIndexOutOfBoundsException in IDataParser.writeRecord
was:
The TweetParser can only take dataset definition with specific order as follow:
{quote}
create type Tweet if not exists as open\{
id: string,
user: TwitterUser,
latitude:double,
longitude:double,
created_at:string,
message_text:string
\};
{quote}
Different order will cause type cast exception since the order is fixed in code.
Also Tweet cannot have extra field, and extra field will cause
ArrayIndexOutOfBoundsException in IDataParser.writeRecord
Summary: TweetParser can only take dataset with specific fields in
specific order (was: TweetParser can only take dataset with fields in specific
order)
> TweetParser can only take dataset with specific fields in specific order
> ------------------------------------------------------------------------
>
> Key: ASTERIXDB-1394
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1394
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: Adapters
> Reporter: Xikui Wang
> Priority: Minor
>
> The TweetParser can only take dataset definition with specific order as
> follow:
> {quote}
> create type Tweet if not exists as open\{
> id: string,
> user: TwitterUser,
> latitude:double,
> longitude:double,
> created_at:string,
> message_text:string
> \};
> {quote}
> Different order will cause type cast exception since the order is fixed in
> code. Also the names of field and number is also fixed, no more or less.
> Also Tweet cannot have extra field, and extra field will cause
> ArrayIndexOutOfBoundsException in IDataParser.writeRecord
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
