[
https://issues.apache.org/jira/browse/DRILL-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728921#comment-13728921
]
Jacques Nadeau commented on DRILL-161:
--------------------------------------
Nice! Interesting solution. I think it is a good first solution. Long term,
I'd prefer to avoid maintaining two separate sets of jars. Questions in my
head:
- Is there we can make the build run tests using these alternative versions to
make sure nothing breaks?
- Does this correctly remove the appropriate dependencies so that common and
protobuf jars are not included as transitive dependencies when using the
rebuffed versions?
- Is there going to be problem with drill-module.conf being overwritten if it
exists in both common and java-exec?
> multiple protoc version support
> -------------------------------
>
> Key: DRILL-161
> URL: https://issues.apache.org/jira/browse/DRILL-161
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Lisen Mu
> Attachments: DRILL-161.patch.0.txt
>
>
> drill depends on 2.5.0 while hadoop 2.0.x depends on 2.4.x.
> multiple versions of protobuf jar library and generated code have to coexist
> in same jvm, to make drill with hadoop 2.0 working happily ever after.
> some possible related keyword:
> jarjar
> osgi
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
