hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <ste...@hortonworks.com>
Subject Re: Order of the fields in REST JSon calls?
Date Thu, 27 Feb 2014 09:47:00 GMT
JSON libs are pretty inconsistent about some things, like what to do if
there is >1 instance of the same field (some pick one, others create an
array). anything that uses a hashmap internally may pick an ordering based
on the hash keys, while other libs do things that make no sense whatsoever:
http://steveloughran.blogspot.co.uk/2012/02/just-because-you-can-rewrite-your.html

I don't think there is a good solution here except avoid some troublespots
(those duplicate entries), warn about orderings, maybe even have tests for
that.


On 26 February 2014 19:09, Jean-Marc Spaggiari <jean-marc@spaggiari.org>wrote:

> Hum. I see
>
>
> https://issues.apache.org/jira/browse/HBASE-9435?focusedCommentId=13782477&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13782477
>
> I will take a quick look to see if we have very simple option to bypass
> current issue with 0.94 without having to make this compatible. Else, will
> just indicate this link to 10617.
>
>
> 2014-02-26 14:04 GMT-05:00 Andrew Purtell <apurtell@apache.org>:
>
> > On Wed, Feb 26, 2014 at 10:55 AM, Jean-Marc Spaggiari <
> > jean-marc@spaggiari.org> wrote:
> >
> > > I'm not sure.
> > >
> > > Here is a comment from the patch: "The patch is backward compatible
> > except
> > > for StorageClusterStatusModel, which is broken anyway. It only shows
> one
> > > node in the liveNodes field." So it might be?
> > >
> > > 2014-02-26 13:48 GMT-05:00 Ted Yu <yuzhihong@gmail.com>:
> > >
> > > > The API changes from HBASE-9435 are incompatible changes, right ?
> > >
> >
> > Yes
> >
> >
> > --
> > Best regards,
> >
> >    - Andy
> >
> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
> > (via Tom White)
> >
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message