[
https://issues.apache.org/jira/browse/HBASE-24356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474658#comment-17474658
]
Tak-Lon (Stephen) Wu commented on HBASE-24356:
----------------------------------------------
{quote}I haven't tested if it could cause any classpath issues if a different
third-party version is used in hbase and connectors.{quote}
hey Peter, I need some suggestion from you to test
I don’t have a good environment to test different third-party versions in the
same classpath, but can you tell me more about this use cases?
IMO the JVM of hbase region server may has its own thirdparty in
HBASE_CLASSPATH, but then the connector e.g. Spark should be able to use
{{spark.driver.userClassPathFirst}} or {{spark.executor.userClassPathFirst}} to
run its thirdparty version if the user classpath is different from
HBASE_CLASSPATH thirdparty. in other words, it depends on how the classpath
environment is being setup for the application that uses the connector.
so, maybe the different thirdparty isn't a concern for this JIRA ?
> Move hbase-connectors to hbase-thirdparty-3.3.0
> -----------------------------------------------
>
> Key: HBASE-24356
> URL: https://issues.apache.org/jira/browse/HBASE-24356
> Project: HBase
> Issue Type: Task
> Components: hbase-connectors
> Affects Versions: hbase-connectors-1.0.1
> Reporter: Peter Somogyi
> Assignee: Tak-Lon (Stephen) Wu
> Priority: Major
> Fix For: hbase-connectors-1.1.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
