db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6117) Extend the Table Functions java interface to pass more query context information from Derby
Date Mon, 03 Feb 2014 15:12:09 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889542#comment-13889542
] 

ASF subversion and git services commented on DERBY-6117:
--------------------------------------------------------

Commit 1563944 from [~rhillegas] in branch 'code/trunk'
[ https://svn.apache.org/r1563944 ]

DERBY-6117: Add a context-aware table function which could be used as an example in user docs;
commit derby-6117-03-aa-ArchiveVTI.diff.

> Extend the Table Functions java interface to pass more query context information from
Derby
> -------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6117
>                 URL: https://issues.apache.org/jira/browse/DERBY-6117
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.8.3.0
>            Reporter: David Vyvyan
>              Labels: derby_triage10_11
>         Attachments: derby-6117-01-aa-AwareVTI.diff, derby-6117-01-ab-AwareVTI.diff,
derby-6117-02-aa-changeColumnNamesInStringColumnVTI.diff, derby-6117-03-aa-ArchiveVTI.diff
>
>
> General requirement is to extend the Table Functions java interface (through RestrictedVTI
or another interface) and pass more context information from Derby to Table Functions - esp
in query execution phase.
> Greater urgency is required for the first 2 items below, especially the ability to access
the original SQL which was available with VTIs. This is critical to the GaianDB project -
we extract HINTs from the query (where we pass meta data like user credentials), and also
extract full original complex predicate expressions (involving functions etc - which cannot
be expressed with a Restriction) - to push on in our query prorogation...
> In order of importance + simplicity:
> --------------------------------------------------
> 1 - Original SQL (this used to be available with VTIs through VTIEnvironment for both
compilation and execution phases)
> 2 - Name of function that was called
> 3 - User Info (ID, etc) - (this can currently be passed in the SQL hint)
> 4 - Richer predicate expressions (incl functions, etc)
> 5 - Context within Join query (e.g. inner or outer table, join type)
> 6 - Other Query Plan information
> 7 - Anything else...?



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message