[jira] [Resolved] (IMPALA-11525) Rename Exec libraries to avoid conflicts with external libraries

["Peter Rozsa (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-11525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Rozsa resolved IMPALA-11525.
----------------------------------
    Resolution: Done

> Rename Exec libraries to avoid conflicts with external libraries
> ----------------------------------------------------------------
>
>                 Key: IMPALA-11525
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11525
>             Project: IMPALA
>          Issue Type: Task
>          Components: Backend
>    Affects Versions: Impala 4.2.0
>            Reporter: Joe McDonnell
>            Assignee: Peter Rozsa
>            Priority: Minor
>
> IMPALA-10800 cleaned up the be/src/exec directory and added directories for various storage formats. These are the new libraries added:
> {noformat}
> Avro
> HBase
> Kudu
> Orc
> Rcfile
> Sequence
> Text{noformat}
> This was a valuable refactor, but several of these library names are very close to the names of external dependencies. Here is a list of similarities:
> {noformat}
> Avro (our library) vs avro (external library)
> Kudu (our library) vs kudu_client (external library)
> Orc (our library) vs orc (external library){noformat}
> It would be better to make the distinction clearer somehow. One option would be to prepend Exec to these libraries like:
> {noformat}
> ExecAvro
> ExecHBase
> ExecKudu
> ExecOrc
> ExecRcfile
> ExecSequence
> ExecText{noformat}
> There are several other good options. These libraries are not exposed externally, so this is entirely up to us.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)