[IMPALA-3926] Reconsider use of LD_LIBRARY_PATH for toolchain libraries

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Impala 2.6.0
• Fix Version/s: Impala 4.0.0
• Component/s: Infrastructure
• Labels: build toolchain
• Target Version: Product Backlog
• Assignee: Tim Armstrong
• Reporter: Matthew Jacobs
• Created: 28/Jul/16 00:54
• Updated: 07/May/20 15:40
• Resolved: 07/May/20 15:40

Description

Right now, impala-config.sh puts a lot of libraries in LD_LIBRARY_PATH, but this can be a problem for binaries that aren't from our builds or explicitly built against these specific libraries. One solution is to move any tools we need into the toolchain and build against these libraries. While this may be a reasonable thing to do (i.e. moving all tools we need into the toolchain), we should consider if setting LD_LIBRARY_PATH for the whole Impala environment is really necessary and the right thing to do (e.g. some people say using LD_LIBRARY_PATH is bad).

Issue Links

• is duplicated by: IMPALA-5755 Undefined symbol in catalog in Ubuntu 16.04 with -so
• is related to: IMPALA-5755 Undefined symbol in catalog in Ubuntu 16.04 with -so
• relates to: IMPALA-3932 virtualenv does not build binary python packages with toolchain