lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (SOLR-1262) DIH needs support for callable statements
Date Mon, 20 Jul 2009 07:37:15 GMT

    [ https://issues.apache.org/jira/browse/SOLR-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733148#action_12733148
] 

Noble Paul edited comment on SOLR-1262 at 7/20/09 12:35 AM:
------------------------------------------------------------

The syntax of a callable statement is distinct from that of a select . So we can just use
that aspect to figure out if it is a callable statement

we can support callable statements with a few restrictions

* Only IN args support
* no return types
* probably no multiple resultsets too


{code}
query="{call getResult( ${x.somevar1} ,${y.somevar2})}"
{code}

Before invoking the callable statements the placeholder locations will be replaced with '?'

as
{code}
{call getResult( ?,?)}
{code}

and setxxx() can be called with the values of ${x.somevar1} and ${y.somevar2}




      was (Author: noble.paul):
    The syntax of a callable statement is distinct from that of a select . So we can just
use that aspect to figure out if it is a callable statement

we can support callable statements with a few restrictions

* Only IN args support


{code}
query="{call getResult( ${x.somevar1} ,${y.somevar2})}"
{code}

Before invoking the callable statements the placeholder locations will be replaced with '?'




  
> DIH needs support for callable statements 
> ------------------------------------------
>
>                 Key: SOLR-1262
>                 URL: https://issues.apache.org/jira/browse/SOLR-1262
>             Project: Solr
>          Issue Type: Improvement
>          Components: contrib - DataImportHandler
>    Affects Versions: 1.3
>         Environment: linux
> mysql
>            Reporter: Abdul Chaudhry
>            Assignee: Noble Paul
>            Priority: Minor
>
> During an indexing run we noticed that we were spending a lot of time creating and tearing
down queries in mysql
> The queries we are using are complex and involve joins spanning across multiple tables.
> We should support prepared statements in the data import handler via the data-config.xml
file - for those databases that support prepared statements.
> We could add a new attribute to the entity entity in dataConfig - say - pquery or preparedQuery
and then pass the prepared statement and have values filled in by the actual queries for each
row using a placeholder - like a ? or something else.
> I would probably start by hacking class JdbcDataSource to try a test but was wondering
if anyone had experienced this or had any suggestions or if there is something in the works
that I missed - I couldn't find any other bugs mentioning using prepared statements for performance.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message