[
https://issues.apache.org/jira/browse/HIVE-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740064#action_12740064
]
Edward Capriolo commented on HIVE-645:
--------------------------------------
@Ashish,
I see your logic on this. My thinking is that key constraints on the
destination table should protect most cases of erroneous data by simply failing
on a duplicate key. The user of this UDF would have to make the call if that is
acceptable for them. Even with a transactional database million row
transactions are not practical, any process could fail midway and leave
artifacts.
In any case, I would like to close up this and some other smaller issues I have
open. So I see a few courses of action here:
* get a new use case scenario with a more concrete coding direction re-code/
create some other utility
* add dboutput as a udf
* add dboutput as a contrib udf
* dont add it, close this jira. Host it myself.
How should we proceed?
> A UDF that can export data to JDBC databases.
> ---------------------------------------------
>
> Key: HIVE-645
> URL: https://issues.apache.org/jira/browse/HIVE-645
> Project: Hadoop Hive
> Issue Type: New Feature
> Components: Query Processor
> Reporter: Edward Capriolo
> Assignee: Edward Capriolo
> Priority: Minor
> Attachments: hive-645-2.patch, hive-645.patch
>
>
> A UDF that can export data to JDBC databases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
