]
Ramesh Reddy resolved TEIID-1569.
---------------------------------
Labels: 7.4CR1 (was: )
Resolution: Done
The developer's guide is updated per suggestion.
Documentation on creating UDF, extending ExecutionFactory and
defining @Translator name should indicate what to do with the translator name
-------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1569
URL:
https://issues.jboss.org/browse/TEIID-1569
Project: Teiid
Issue Type: Enhancement
Components: Documentation
Affects Versions: 7.1.1
Reporter: Van Halbert
Assignee: Ramesh Reddy
Priority: Minor
Labels: 7.4CR1
Fix For: 7.4
A user was trying to follow the documentation
(
http://docs.jboss.org/teiid/7.3.0.Final/developer-guide/en-US/html_single...) on
creating a UDF and have it pushed down to the source. But they didn't make the
correlation between the process of extending the ExecutionFactory and then having to use
the defined @Translator name. It wasn't obvious to them. Therefore, I think it
would be good to indicated in the "Required" segment of the example of extending
the Oracle Connector:
Required - extend the OracleExecutionFactory and add SCORE and CONTAINS as supported
functions. For this example, we'll call the class MyOracleExecutionFactory. Add the
org.teiid.translator.Translator annotation to the class, e.g.
@Translator(name="myoracle")
------
Add a follow on sentence to indicate that the @Translator name (i.e.,
"myoracle") is the name to assign to the translator for the physical model for
which the custom translator will be used (or something like that).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: