You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@asterixdb.apache.org by "Xikui Wang (JIRA)" <ji...@apache.org> on 2016/08/25 14:57:20 UTC

[jira] [Commented] (ASTERIXDB-1318) TweetParser should be able to translate all JSON field to ADM

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

Xikui Wang commented on ASTERIXDB-1318:
---------------------------------------

This one is fixed in the latest change.

> TweetParser should be able to translate all JSON field to ADM
> -------------------------------------------------------------
>
>                 Key: ASTERIXDB-1318
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1318
>             Project: Apache AsterixDB
>          Issue Type: Bug
>            Reporter: Jianfeng Jia
>            Assignee: Xikui Wang
>
> The internal TweetParser have some limitations. 
> 1. We only pick a few JSON fields, e.g. user, geolocation, message. I need the place field. Also, there are also some other fields the other application may also interested in. As a service provided by us, we should cut any information from the original JSON file.
> 2. The text fields always call getNormalizedString() to filter out the not-ASCII chars, which is a big loss of information. Even for English messages there are emojis which are not “normal”.



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