[
https://issues.apache.org/jira/browse/TRAFODION-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049450#comment-15049450
]
ASF GitHub Bot commented on TRAFODION-1581:
-------------------------------------------
Github user zellerh commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/218#discussion_r47159287
--- Diff: core/sql/sqludr/sqludr.cpp ---
@@ -7761,7 +7761,7 @@ void UDR::processData(UDRInvocationInfo &info,
*
* This method is called in debug Trafodion builds when certain
* flags are set in the UDR_DEBUG_FLAGS CQD (CONTROL QUERY DEFAULT).
- * See
https://wiki.trafodion.org/wiki/index.php/Tutorial:_The_object-oriented_UDF_interface#Debugging_UDF_code
+ * See
https://cwiki.apache.org/confluence/display/TRAFODION/Tutorial%3A+The+object-oriented+UDF+interface#Tutorial:Theobject-orientedUDFinterface-DebuggingUDFcode
--- End diff --
Gunnar commented on those wiki pages that are moving, saying that no more
changes should be made. He did not comment on this one, so I assume it will
stay on the wiki.
> Add a TMUDF that can return a JDBC result set as table-valued output
> --------------------------------------------------------------------
>
> Key: TRAFODION-1581
> URL: https://issues.apache.org/jira/browse/TRAFODION-1581
> Project: Apache Trafodion
> Issue Type: Sub-task
> Components: sql-general
> Affects Versions: 1.3-incubating
> Reporter: Hans Zeller
> Assignee: Hans Zeller
> Fix For: 2.0-incubating
>
>
> One way to read data from other data sources would be a Trafodion TMUDF that
> takes a connection string, an SQL statement and other necessary info as an
> input, connects to a JDBC data source, prepares the statement, and returns
> the result set as a table-valued output. This would enable a basic connector
> for many data sources, including Spark, Drill and Kafka.
> Specifically, I would like to add a "predefined" TMUDF to Trafodion that
> takes the following parameters:
> 1. The name of a jar with a JDBC driver.
> 2. A connection string to use
> 3. The class name of the driver
> 4. A user id
> 5. A password
> 6. The type of processing to do (right now only one type is supported)
> 7. Info depending on the type.
> The first type of processing I would like to add is "source", and it does the
> following: It accepts a list of SQL statements to execute. Only one of these
> statements can return a result set. The data in the result set will be
> returned as table-valued output.
> Future processing types could do a parallel select like ODB does or they
> could insert into a table on the system identified by the JDBC driver info.
> All parameters need to be compile-time constants, so that the UDF can connect
> to the data source at compile time and prepare the statement. Based on the
> prepared statement, it will determine number, names and SQL types of the
> column(s) of the table-valued result.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
