[
https://issues.apache.org/jira/browse/NIFI-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14581841#comment-14581841
]
Mark Payne commented on NIFI-626:
---------------------------------
Toivo,
Excellent, thanks! I think the NPE was related to the way you're building up
the URL if you choose "Other DB". When you're able, can you look at NIFI-677
and see if that seems like a reasonable thing to do? You may have some insights
from developing this that I don't have. So if it does make sense I think it's a
good direction to go. If it doesn't make sense, then let me know and I'll close
it out with an explanation. I bring it up now because I think that if we
implement NIFI-677, it will take care of the NPE anyway.
Thanks!
-Mark
> ExecuteSQL processor for executing arbitrary SQL queries
> --------------------------------------------------------
>
> Key: NIFI-626
> URL: https://issues.apache.org/jira/browse/NIFI-626
> Project: Apache NiFi
> Issue Type: Sub-task
> Affects Versions: 0.2.0
> Reporter: Toivo Adams
> Assignee: Toivo Adams
> Labels: patch
> Fix For: 0.2.0
>
> Attachments:
> 0001-NIFI-626-Code-cleanup-to-adhere-to-NiFi-coding-style.patch,
> NIFI-626_25may2015.patch, NIFI-626_26may2015.patch, NIFI-626_31may2015.patch
>
>
> For example query can be:
> SELECT * FROM orders WHERE orderId = '${order.id}'
> where ${order.id} is FlowFile attribute.
> Result will serialized using Avro.
> Avro gives as possibility to have query Resultset metadata (column name and
> types) included in FlowFile.
> Also Avro should allow streaming.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
