[
https://issues.apache.org/jira/browse/HBASE-21229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16627638#comment-16627638
]
Sean Busbey commented on HBASE-21229:
-------------------------------------
I'd say probably the script that runs the nightly test should take a parameter
for an hbase shaded client jar to use, then attempt to use that to build + run
the example application again (presuming it covers the breakage that was seen
in HBASE-20993). unless the hadoop bits are a problem, in which case we'll need
another simple example program.
Then in our actual use in the nightly tests we can pass in whatever version
client jar it is we want, probably 1.2.0.
> Add a nightly check that client-server wire compatibility works
> ---------------------------------------------------------------
>
> Key: HBASE-21229
> URL: https://issues.apache.org/jira/browse/HBASE-21229
> Project: HBase
> Issue Type: Improvement
> Components: test
> Affects Versions: 3.0.0, 1.5.0, 1.3.3, 1.2.8, 2.2.0, 1.4.8, 2.1.1, 2.0.3
> Reporter: Sean Busbey
> Priority: Major
>
> From HBASE-20993:
> {quote}
> bq. Good reminder that we lack a unit test for wire compatibility. I wonder
> how hard it would be to grab the 1.2 shaded client artifact and use it to
> talk with the server code at head of branch.
> We could add a nightly test that did this pretty easily. Essentially we could
> just add it as an additional step in [the test that starts up a 1-node
> cluster and runs an example
> program|https://github.com/apache/hbase/blob/master/dev-support/hbase_nightly_pseudo-distributed-test.sh].
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
