[
https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010914#comment-17010914
]
Sandeep Guggilam commented on PHOENIX-5607:
-------------------------------------------
[~larsh] The challenge is more about downloading a specific client version. As
discussed offline, here are the options:
# Check in the client jar in the GIT repo. The downside is that it would
increase the binary size if we checkin more client versions as each client
version jar is ~100MB
# Download the tar ball from the apache repository and extract out the client
jar. Downside is that we are downloading the entire tar ball even though we
just need a specific client jar
# Use mvn command to get a specific phoenix client jar but the challenge is
more about getting the MAVEN home for a given environment
# Add the client version jar as a dependency in the pom file but the challenge
is more about getting the Maven local repository location though in most cases
it wouldn't change from <user.home>/.m2 but still there is an assumption
involved here
Suggestions ?
[~ckulkarni] [~gjacoby]
> Client-server backward compatibility tests
> -------------------------------------------
>
> Key: PHOENIX-5607
> URL: https://issues.apache.org/jira/browse/PHOENIX-5607
> Project: Phoenix
> Issue Type: Test
> Affects Versions: 4.15.0
> Reporter: Lars Hofhansl
> Priority: Blocker
> Labels: phoenix-hardening
> Fix For: 4.16.0
>
>
> Filing this as a blocker for 4.16.0.
> As we've seen with the various failed attempts to release 4.15.0 Phoenix'
> backwards compatibility story is weak, and lacks tests - in fact there're no
> tests.
> We should not allow to ship 4.16.0 without improving that and without tests.
> [~ckulkarni], [~gjacoby] , FYI, what we discussed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
