You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/11/03 00:23:00 UTC
[jira] [Updated] (IMPALA-1957) Add verification tool for external
data sources
[ https://issues.apache.org/jira/browse/IMPALA-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong updated IMPALA-1957:
----------------------------------
Priority: Trivial (was: Minor)
> Add verification tool for external data sources
> -----------------------------------------------
>
> Key: IMPALA-1957
> URL: https://issues.apache.org/jira/browse/IMPALA-1957
> Project: IMPALA
> Issue Type: New Feature
> Components: Infrastructure
> Affects Versions: Impala 1.4, Impala 2.0
> Reporter: Matthew Jacobs
> Priority: Trivial
> Labels: supportability
>
> It would be helpful to provide a tool to perform some sanity checks on external data sources.
> A few initial ideas:
> 1) Verify the data source handles various valid calling patters (e.g. Init()->Prepare()->GetNext()->Close(), Init()->Close(), Init()->Prepare()->Close()).
> 2) Verify returned structures are valid and internally consistent.
> 3) Check if the data source is leaking, e.g. can we load the jar, call the data source, unload the jar-- i.e. did any objects remain in memory such that the classloader couldn't be unloaded?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org