[
https://issues.apache.org/jira/browse/IMPALA-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17763270#comment-17763270
]
ASF subversion and git services commented on IMPALA-12424:
----------------------------------------------------------
Commit bc83d46a9a1b6b4a3ca859d3a2835185f4473427 in impala's branch
refs/heads/master from Steve Carlin
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=bc83d46a9 ]
IMPALA-12424: Allow third party JniFrontend interface.
This patch allows a third party to inject their own frontend
class instead of using the default JniFrontend included in the
project.
The test case includes an interface that runs queries as normal
except for the "select 1" query which gets changed to "select 42".
Change-Id: I89e677da557b39232847644b6ff17510e2b3c3d5
Reviewed-on: http://gerrit.cloudera.org:8080/20459
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Allow third party extensibility for JniFrontend
> -----------------------------------------------
>
> Key: IMPALA-12424
> URL: https://issues.apache.org/jira/browse/IMPALA-12424
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Reporter: Steve Carlin
> Assignee: Steve Carlin
> Priority: Major
> Fix For: Impala 4.3.0
>
>
> The JniFrontend java class is called through Jni on the backend. We should
> allow a developer to create their own JniFrontend class if they want to use
> their own planner to create an Impala request
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
