[
https://issues.apache.org/jira/browse/NIFI-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14581907#comment-14581907
]
Toivo Adams commented on NIFI-626:
----------------------------------
Mark,
You are right, culprit is how URL is built.
NPE is easily reproducible.
It won’t work because "Other DB" don’t have URL template defined.
And it seems it’s more reasonable to let user Enter correct Connection URL,
instead of creating URL from template.
Because we don’t know "Other DB" URL template format anyway and it’s weird to
require URL template from user when "Other DB" is selected.
My initial idea was to help ‘end user’ (DataFlow Manager?) to enter correct
values.
But it seems ‘end user’ here should be a person who must know such details
anyway.
I will do needed corrections.
Thanks
Toivo
> 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)
