You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@asterixdb.apache.org by Wail Alkowaileet <wa...@gmail.com> on 2016/11/03 11:11:43 UTC
Orderedlist vs. unorderedlist as default open type
Dears,
Currently, unordered list is the default type of JSON array if it resides
in the open part.
That means the user won't be able to access any item of the list using
index. Which is unexpected. At least for my colleagues who use AsterixDB. I
think only JSON types should appear in the open part.
Also, I believe there's inconsistency. When we do *group by .. with ..*
the result of "with" clause is ordered list.
Any thoughts ?
--
*Regards,*
Wail Alkowaileet
Re: Orderedlist vs. unorderedlist as default open type
Posted by Mike Carey <dt...@gmail.com>.
Seems like we should fix it there. (But it's a little scary that it's
feed-specific - it seems like the code should be structured in a way
that would share this decision?)
On 11/3/16 8:18 AM, Wail Alkowaileet wrote:
> My mistake... That's only for Twitter feed.
>
> On Nov 3, 2016 14:11, "Wail Alkowaileet" <wa...@gmail.com> wrote:
>
>> Dears,
>>
>> Currently, unordered list is the default type of JSON array if it resides
>> in the open part.
>> That means the user won't be able to access any item of the list using
>> index. Which is unexpected. At least for my colleagues who use AsterixDB. I
>> think only JSON types should appear in the open part.
>>
>> Also, I believe there's inconsistency. When we do *group by .. with ..*
>> the result of "with" clause is ordered list.
>>
>> Any thoughts ?
>>
>> --
>>
>> *Regards,*
>> Wail Alkowaileet
>>
Re: Orderedlist vs. unorderedlist as default open type
Posted by Wail Alkowaileet <wa...@gmail.com>.
My mistake... That's only for Twitter feed.
On Nov 3, 2016 14:11, "Wail Alkowaileet" <wa...@gmail.com> wrote:
> Dears,
>
> Currently, unordered list is the default type of JSON array if it resides
> in the open part.
> That means the user won't be able to access any item of the list using
> index. Which is unexpected. At least for my colleagues who use AsterixDB. I
> think only JSON types should appear in the open part.
>
> Also, I believe there's inconsistency. When we do *group by .. with ..*
> the result of "with" clause is ordered list.
>
> Any thoughts ?
>
> --
>
> *Regards,*
> Wail Alkowaileet
>
Re: Orderedlist vs. unorderedlist as default open type
Posted by Xikui Wang <xi...@uci.edu>.
That's an implementation mistake in TweetParser. Sorry about that. Will
submit a fix soon.
On Thu, Nov 3, 2016 at 10:17 AM, Mike Carey <dt...@gmail.com> wrote:
> This seems odd to me too - in the absence of schema, since JSON only has
> ordered lists, it seems like that would be the natural default.
>
>
>
> On 11/3/16 4:11 AM, Wail Alkowaileet wrote:
>
>> Dears,
>>
>> Currently, unordered list is the default type of JSON array if it resides
>> in the open part.
>> That means the user won't be able to access any item of the list using
>> index. Which is unexpected. At least for my colleagues who use AsterixDB.
>> I
>> think only JSON types should appear in the open part.
>>
>> Also, I believe there's inconsistency. When we do *group by .. with ..*
>> the result of "with" clause is ordered list.
>>
>> Any thoughts ?
>>
>>
>
Re: Orderedlist vs. unorderedlist as default open type
Posted by Mike Carey <dt...@gmail.com>.
This seems odd to me too - in the absence of schema, since JSON only has
ordered lists, it seems like that would be the natural default.
On 11/3/16 4:11 AM, Wail Alkowaileet wrote:
> Dears,
>
> Currently, unordered list is the default type of JSON array if it resides
> in the open part.
> That means the user won't be able to access any item of the list using
> index. Which is unexpected. At least for my colleagues who use AsterixDB. I
> think only JSON types should appear in the open part.
>
> Also, I believe there's inconsistency. When we do *group by .. with ..*
> the result of "with" clause is ordered list.
>
> Any thoughts ?
>