[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo updated BOOKKEEPER-340:
---------------------------------

    Attachment: BOOKKEEPER-340.patch

attach a patch for testing backward compatibility between different hedwig 
versions. similar as what we did for bookkeeper-server.

this patch introduces two test cases, one is for message bound. 4.0.0 version 
doesn't support message bound. a higher client talks with it, the message bound 
doesn't take effects.

the other one is publish interface. a current version client talks with 4.1.0 
server, no message seq id would be returned.

besides that, there are some minor changes:

1) this patch generates bookkeeper tests jar for hedwig test. so tests jar 
would exist in target directory after 'mvn package'. so improve bin/bookkeeper 
script to exclude tests jar in CLASSPATH.

2) remove tabs in hedwig-server/pom.xml since we are touching the file.

3) exclude 'bookkeeper-server' in bookkeeper-compat-xxx dependency. otherwise, 
an old version of bookkeeper jar would be put in bookkeeper-server/lib 
directory when running 'mvn package'.
                
> Test backward compatibility for hedwig between different versions.
> ------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-340
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-340
>             Project: Bookkeeper
>          Issue Type: Improvement
>            Reporter: Sijie Guo
>            Assignee: Sijie Guo
>             Fix For: 4.2.0
>
>         Attachments: BOOKKEEPER-340.patch
>
>
> we should provide backward compatibility testing for hedwig between different 
> versions. as what we did in BOOKKEEPER-292 for bookkeeper. I had did it in 
> BOOKKEEPER-332, but it would be better to provide here. since BOOKKEEPER-331 
> also need it for some backward compatibility testing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to