[JBoss JIRA] (TEIID-4297) Add UDF functions based on OSDQ for POC
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4297?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4297:
-------------------------------------
This is more for how to integrate, there was not much functionality in terms of functions yet. I would say we need to drive it little further before we document it.
> Add UDF functions based on OSDQ for POC
> ---------------------------------------
>
> Key: TEIID-4297
> URL: https://issues.jboss.org/browse/TEIID-4297
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 9.1
>
>
> Please add following UDF functions to Teiid library based on maven module
> http://search.maven.org/#search%7Cga%7C1%7Carrahtec
> The UDF functions needs to from this class below
> {code}
> public class Maskutil {
> /**
> * @param a
> * The string that need to randomize
> * vivek singh' will become 'ihg vkeivh'
> */
> public static String toRandomValue(String a) {
> return ShuffleRTM.shuffleString(a);
> }
> /**
> * @param a
> * This function will retrun MD5 hashcode of the string
> * @return String
> */
> public static String toHashValue(String a) {
> if (a == null)
> return "d41d8cd98f00b204e9800998ecf8427e"; // null MD5 value
> return ResultsetToRTM.getMD5(a).toString();
> }
> /**
> * @param a
> * This function will return digit characters of the string
> * @return
> *
> */
> public static String toDigitValue(String a) {
> return StringCaseFormatUtil.digitString(a);
> }
> }
> {code}
> for example Teiid should have UDF functions like
> {code}
> string random(string)
> string hash(string)
> string digit(string)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4297) Add UDF functions based on OSDQ for POC
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4297?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4297:
---------------------------------------
Are we looking to add docs/release notes as well, or do you want to keep this undocumented for now?
> Add UDF functions based on OSDQ for POC
> ---------------------------------------
>
> Key: TEIID-4297
> URL: https://issues.jboss.org/browse/TEIID-4297
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 9.1
>
>
> Please add following UDF functions to Teiid library based on maven module
> http://search.maven.org/#search%7Cga%7C1%7Carrahtec
> The UDF functions needs to from this class below
> {code}
> public class Maskutil {
> /**
> * @param a
> * The string that need to randomize
> * vivek singh' will become 'ihg vkeivh'
> */
> public static String toRandomValue(String a) {
> return ShuffleRTM.shuffleString(a);
> }
> /**
> * @param a
> * This function will retrun MD5 hashcode of the string
> * @return String
> */
> public static String toHashValue(String a) {
> if (a == null)
> return "d41d8cd98f00b204e9800998ecf8427e"; // null MD5 value
> return ResultsetToRTM.getMD5(a).toString();
> }
> /**
> * @param a
> * This function will return digit characters of the string
> * @return
> *
> */
> public static String toDigitValue(String a) {
> return StringCaseFormatUtil.digitString(a);
> }
> }
> {code}
> for example Teiid should have UDF functions like
> {code}
> string random(string)
> string hash(string)
> string digit(string)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4297) Add UDF functions based on OSDQ for POC
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4297?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-4297.
---------------------------------
Resolution: Done
Initial POC should be done now.
> Add UDF functions based on OSDQ for POC
> ---------------------------------------
>
> Key: TEIID-4297
> URL: https://issues.jboss.org/browse/TEIID-4297
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 9.1
>
>
> Please add following UDF functions to Teiid library based on maven module
> http://search.maven.org/#search%7Cga%7C1%7Carrahtec
> The UDF functions needs to from this class below
> {code}
> public class Maskutil {
> /**
> * @param a
> * The string that need to randomize
> * vivek singh' will become 'ihg vkeivh'
> */
> public static String toRandomValue(String a) {
> return ShuffleRTM.shuffleString(a);
> }
> /**
> * @param a
> * This function will retrun MD5 hashcode of the string
> * @return String
> */
> public static String toHashValue(String a) {
> if (a == null)
> return "d41d8cd98f00b204e9800998ecf8427e"; // null MD5 value
> return ResultsetToRTM.getMD5(a).toString();
> }
> /**
> * @param a
> * This function will return digit characters of the string
> * @return
> *
> */
> public static String toDigitValue(String a) {
> return StringCaseFormatUtil.digitString(a);
> }
> }
> {code}
> for example Teiid should have UDF functions like
> {code}
> string random(string)
> string hash(string)
> string digit(string)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4374) Procedure missing for an OData metadata request to a Swagger VDB
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4374?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-4374.
---------------------------------
Fix Version/s: 9.1
Resolution: Done
Labels: Beta1 (was: )
Luckily in this case your BODY was defined as Object type with simple parameters, so I could inline individual properties as parameters to the procedure. If this was an Array that would not be possible. I added the extra checking for this step.
I am not sure how the "apache.commons.io" dependency got introduced (must be some version upgrade) but I added it to the dependencies list also, so that you do not have to copy the module. (You should report these kind when you find them)
While testing this, it also uncovered couple issues with TEIID-2715 which I fixed on master.
> Procedure missing for an OData metadata request to a Swagger VDB
> ----------------------------------------------------------------
>
> Key: TEIID-4374
> URL: https://issues.jboss.org/browse/TEIID-4374
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.0, 9.0.1, 9.0.2
> Environment: Windows 10 Pro x64
> Java 8
> Reporter: Van Dillon
> Assignee: Ramesh Reddy
> Labels: Beta1
> Fix For: 9.1
>
> Attachments: resource-adapter-rhq.xml, rhq-metadata.xml, rhq-vdb.xml, swagger.json
>
>
> When a REST PUT path defined in Swagger has a path parameter and a body it does not appear in OData metadata.
> See the attached swagger.json for an example. The operation 'executeOperation' does not appear in OData metadata.
> The code that determines if a procedure is allowed is in:
> org.teiid.olingo.service.ODataSchemaBuilder.allowedProcedure()
> The comment seems to indicate that as long as there is only a single LOB, multiple 'in' parameters are allowed. But the actual code does not allow any other 'in' parameters if there is a LOB parameter.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4374) Procedure missing for an OData metadata request to a Swagger VDB
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4374?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4374:
-------------------------------------
All actions can only take single body parameter in OData as parameter input. See http://docs.oasis-open.org/odata/odata-json-format/v4.0/errata03/os/odata... the support for the PATH based parameters for ACTION is not there, thus it can not handle the executeOperation.
Two way to make it work is, either change BODY parameter to PATH, or remove the PATH parameter in the Swagger's executeOperation method and fold that into BODY parameter's schema.
I also need to give little more thought as to if there are anything else we can do to support this?
> Procedure missing for an OData metadata request to a Swagger VDB
> ----------------------------------------------------------------
>
> Key: TEIID-4374
> URL: https://issues.jboss.org/browse/TEIID-4374
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.0, 9.0.1, 9.0.2
> Environment: Windows 10 Pro x64
> Java 8
> Reporter: Van Dillon
> Assignee: Ramesh Reddy
> Attachments: resource-adapter-rhq.xml, rhq-metadata.xml, rhq-vdb.xml, swagger.json
>
>
> When a REST PUT path defined in Swagger has a path parameter and a body it does not appear in OData metadata.
> See the attached swagger.json for an example. The operation 'executeOperation' does not appear in OData metadata.
> The code that determines if a procedure is allowed is in:
> org.teiid.olingo.service.ODataSchemaBuilder.allowedProcedure()
> The comment seems to indicate that as long as there is only a single LOB, multiple 'in' parameters are allowed. But the actual code does not allow any other 'in' parameters if there is a LOB parameter.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4297) Add UDF functions based on OSDQ for POC
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4297?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4297:
-------------------------------------
Revised older commit with simpler approach using {quote}@TeiidFunction{quote}. created a new module called "data-quality" to keep this pushing further with rich capabilities.
As per binary dependency on Teiid kit, I could not achieve that, as the Annotations were not showing up, and I can't use module classloader in "engine". There may be other techniques to solve this, but nothing striked off my mind.
Latest commit can be found here.
https://github.com/teiid/teiid/commit/09af025e597e14985b7d46162bfb467401b...
> Add UDF functions based on OSDQ for POC
> ---------------------------------------
>
> Key: TEIID-4297
> URL: https://issues.jboss.org/browse/TEIID-4297
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 9.1
>
>
> Please add following UDF functions to Teiid library based on maven module
> http://search.maven.org/#search%7Cga%7C1%7Carrahtec
> The UDF functions needs to from this class below
> {code}
> public class Maskutil {
> /**
> * @param a
> * The string that need to randomize
> * vivek singh' will become 'ihg vkeivh'
> */
> public static String toRandomValue(String a) {
> return ShuffleRTM.shuffleString(a);
> }
> /**
> * @param a
> * This function will retrun MD5 hashcode of the string
> * @return String
> */
> public static String toHashValue(String a) {
> if (a == null)
> return "d41d8cd98f00b204e9800998ecf8427e"; // null MD5 value
> return ResultsetToRTM.getMD5(a).toString();
> }
> /**
> * @param a
> * This function will return digit characters of the string
> * @return
> *
> */
> public static String toDigitValue(String a) {
> return StringCaseFormatUtil.digitString(a);
> }
> }
> {code}
> for example Teiid should have UDF functions like
> {code}
> string random(string)
> string hash(string)
> string digit(string)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4379) OData entity row created twice
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4379:
-------------------------------------
Summary: OData entity row created twice
Key: TEIID-4379
URL: https://issues.jboss.org/browse/TEIID-4379
Project: Teiid
Issue Type: Quality Risk
Components: OData
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 9.1
The logic to detect duplicate entities in the simple case of no duplicates causes each entity row to be created twice.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months