[GitHub] [spark] LuciferYang commented on pull request #38609: [WIP][SPARK-40593][CONNECT] Add profile to make user can specify custom `protocExecutable` and `pluginExecutable` when building connect module

[GitBox <gi...@apache.org>]

LuciferYang commented on PR #38609:
URL: https://github.com/apache/spark/pull/38609#issuecomment-1311156538

   @HyukjinKwon 
   
   As I mentioned in SPARK-40593
   
   The default glibc version in CentOs6 and CentOs7 is 2.12, but glibc 2.14 is required at least when build `connect` module, so the following compilation errors will occur when build `connect`  module on CentOs6&CentOs7:
   
   ```
   [ERROR] PROTOC FAILED: /home/disk0/spark-source/connect/target/protoc-plugins/protoc-3.21.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /home/disk0/spark-source/connect/target/protoc-plugins/protoc-3.21.1-linux-x86_64.exe)
   /home/disk0/spark-source/connect/target/protoc-plugins/protoc-3.21.1-linux-x86_64.exe: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.18' not found (required by /home/disk0/spark-source/connect/target/protoc-plugins/protoc-3.21.1-linux-x86_64.exe)
   /home/disk0/spark-source/connect/target/protoc-plugins/protoc-3.21.1-linux-x86_64.exe: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.14' not found (required by /home/disk0/spark-source/connect/target/protoc-plugins/protoc-3.21.1-linux-x86_64.exe)
   /home/disk0/spark-source/connect/target/protoc-plugins/protoc-3.21.1-linux-x86_64.exe: /usr/lib64/libstdc++.so.6: version `CXXABI_1.3.5' not found (required by /home/disk0/spark-source/connect/target/protoc-plugins/protoc-3.21.1-linux-x86_64.exe) 
   ```
   
   In the current draft, I added a new profile to let the user specify user-defined `protocExecutable` and `pluginExecutable` for workaourd, for exmaple 
   
   ```
   export CONNECT_PROTOC_EXEC_PATH = pathToProtocExecutable
   export CONNECT_PLUGIN_EXEC_PATH = pathToPluginExecutable
   mvn clean install -DskipTests connector/connect -am 
   ```
   
   
   Currently, only Maven related parts are implemented in draft. Do we accept this way to workaround?
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org