Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of andrew.purtell@gmail.com
 designates 209.85.213.176 as permitted sender)
Subject: Re: REST Interface: Required ordering of JSON name/value pairs when
 performing Insert/Update
References: <y2sa06fb5761004201237p9bf35decr7fc994b6a9169dd4@mail.gmail.com>
 <682550.37360.qm@web65508.mail.ac4.yahoo.com>
 <CANZa=Gtz2bgUdhknD9V+PRsdXWLhM2j8-7FgupNdrDTCLm_N4A@mail.gmail.com>
From: Andrew Purtell <andrew.purtell@gmail.com>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
In-Reply-To: 
 <CANZa=Gtz2bgUdhknD9V+PRsdXWLhM2j8-7FgupNdrDTCLm_N4A@mail.gmail.com>
Message-Id: <CE305ACE-2773-450E-AEEB-DE367C524011@gmail.com>
Date: Sun, 3 Jun 2012 12:32:06 +0200
Cc: "hbase-user@hadoop.apache.org" <hbase-user@hadoop.apache.org>,
 "apurtell@apache.org" <apurtell@apache.org>
To: "user@hbase.apache.org" <user@hbase.apache.org>
Mime-Version: 1.0 (1.0)

Thanks for the report.

I reopened the JIRA. It might be the best we can do is make a documentation u=
pdate.

I'm in Berlin this week for Buzzwords, might not get a chance to look at thi=
s until late this week or early next.=20

    - Andy

On Jun 3, 2012, at 11:51 AM, Nick Dimiduk <ndimiduk@gmail.com> wrote:

> Hi Andy,
>=20
> What's the status of this bug? The JIRA says it was resolved in 0.20.5 and=

> 0.90.0 but I'm able to repro in 0.92.0.
>=20
> When I:
>=20
> $ curl -v -XPUT \
>  -H "Content-Type: application/json" \
>  http://localhost:9999/users/TheRealMT/info:password \
>  -d '{
>    "Row": [
>        {
>            "Cell": [
>                {
> *                    "@column": "aW5mbzpwYXNzd29yZA=3D=3D",*
> *                    "$": "NzBOQHJJIE4wIDcwdDBSMA=3D=3D"*
>                }
>            ],
>            "@key": "VGhlUmVhbE1U"
>        }
>    ]
> }'
>=20
> The logs show:
>=20
> 12/06/03 02:43:16 DEBUG rest.RowResource: PUT
> http://localhost:9999/users/TheRealMT/info:password
> 12/06/03 02:43:16 DEBUG rest.RowResource: PUT
> {"totalColumns":1,"families":{"info":[{"timestamp":9223372036854775807,"qu=
alifier":"password",
> *"vlen":16*}]},"row":"TheRealMT"}
>=20
> And the write is successful.
>=20
> But if I:
>=20
> $ curl -v -XPUT \
>  -H "Content-Type: application/json" \
>  http://localhost:9999/users/TheRealMT/info:password \
>  -d '{
>    "Row": [
>        {
>            "Cell": [
>                {
> *                    "$": "NzBOQHJJIE4wIDcwdDBSMA=3D=3D",*
> *                    "@column": "aW5mbzpwYXNzd29yZA=3D=3D"*
>                }
>            ],
>            "@key": "VGhlUmVhbE1U"
>        }
>    ]
> }'
>=20
> The log shows:
>=20
> 12/06/03 02:46:22 DEBUG rest.RowResource: PUT
> http://localhost:9999/users/TheRealMT/info:password
> 12/06/03 02:46:22 DEBUG rest.RowResource: PUT
> {"totalColumns":1,"families":{"info":[{"timestamp":9223372036854775807,"qu=
alifier":"password",
> *"vlen":0*}]},"row":"TheRealMT"}
>=20
> And my cell is now empty.
>=20
> For reference:
>=20
> $ curl http://localhost:9999/version
> rest 0.0.2 [JVM: Apple Inc. 1.6.0_31-20.6-b01-415] [OS: Mac OS X 10.7.4
> x86_64] [Server: jetty/6.1.26] [Jersey: 1.4]
> $ curl http://localhost:9999/version/cluster
> 0.92.0
>=20
> Thanks,
> -n
>=20
> On Tue, Apr 20, 2010 at 3:08 PM, Andrew Purtell <apurtell@apache.org> wrot=
e:
>=20
>> I filed a JIRA for this and will take a look at it soon:
>> https://issues.apache.org/jira/browse/HBASE-2475
>>=20
>> Thanks for the report, very helpful.
>>=20
>>> In the equivalent XML notation, the ordering is
>>> specifically required per the schema.
>>=20
>> ... and Jersey adds a marshaller and unmarshaller to the JAXB framework t=
o
>> produce JSON. This is an artifact of jersey-json or something dumb we did=

>> when hooking up JAXB.
>>=20
>>  - Andy
>>=20
>>> From: Tyler Coffin
>>> Subject: REST Interface: Required ordering of JSON name/value pairs when=

>> performing Insert/Update
>>>=20
>>> I am using the Stargate REST interface to HBase for
>>> inserting data. When using JSON to transmit the query content,
>>> I have found that specific ordering of key/value pairs within
>>> the JSON string is required in order for the query to succeed
>>> (otherwise a response of 'HTTP/1.1 500 Row key is invalid' error
>>> is thrown if "key" and "Cell" are reversed).
>>>=20
>>> Example:
>>> This string receives the above error:
>>>=20
>> {"Row":[{"Cell":[{"column":"bWVzc2FnZTptc2c=3D","$":"Zm9vYmFy"}],"key":"M=
TIzNAo=3D"}]}
>>> This is the valid equivalent string:
>>>=20
>> {"Row":[{"key":"MTIzNAo=3D","Cell":[{"column":"bWVzc2FnZTptc2c=3D","$":"Z=
m9vYmFy"}]}]}
>>> As you can see the only difference between these two
>>> instances is that
>>> the "key" and "Cell" name/value pairs have their order
>>> reversed.
>>>=20
>>> In the equivalent XML notation, the ordering is
>>> specifically required per the schema.
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20