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

ASF GitHub Bot commented on STORM-699:
--------------------------------------

GitHub user Parth-Brahmbhatt opened a pull request:

    https://github.com/apache/storm/pull/458

    STORM-699: storm-jdbc should support custom insert queries.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Parth-Brahmbhatt/incubator-storm STORM-699

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/storm/pull/458.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #458
    
----
commit 3cad1c71bc274d097bfeb6691145bbc31e8e8a91
Author: Parth Brahmbhatt <brahmbhatt.pa...@gmail.com>
Date:   2015-03-07T02:46:10Z

    STORM-699: storm-jdbc should support custom insert queries.

----


> storm-jdbc should support customer insert queries.
> --------------------------------------------------
>
>                 Key: STORM-699
>                 URL: https://issues.apache.org/jira/browse/STORM-699
>             Project: Apache Storm
>          Issue Type: Improvement
>    Affects Versions: 0.10.0
>            Reporter: Parth Brahmbhatt
>            Assignee: Parth Brahmbhatt
>            Priority: Minor
>
> Currently storm-jdbc insert bolt/state only supports to specify a table name 
> and constructs a query of the form "insert into tablename values(?,?,?)" 
> based on table's schema. This fails to support use cases like "insert into as 
> select * from" or special cases like Phoenix that has a jdbc driver but only 
> supports "upsert into". 
> We should add a way so the users can specify their own custom query for the 
> insert bolt.  This was already pointed out by [~revans2] during the PR review 
> and we now have concrete cases that will be benefited by this feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to