October 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4792) Unable to use WHERE clause against a JDG data source - ISPN000402: The type com.redhat.demo.sko.pojo.Call has no property named .....

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4792?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4792. ----------------------------------- Resolution: Out of Date Marking the upstream issue as out of date. > Unable to use WHERE clause against a JDG data source - ISPN000402: The type com.redhat.demo.sko.pojo.Call has no property named ..... > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-4792 > URL: https://issues.jboss.org/browse/TEIID-4792 > Project: Teiid > Issue Type: Bug > Components: JDG Connector > Environment: Mac OS > JDV 6.3.4 > JDG 6.6.1 > JBDS 10.3.0 with JBDSIS 10.0.2 > Reporter: Cojan van Ballegooijen > Assignee: Van Halbert > Priority: Major > Attachments: Call_JDG_Module.zip, ChurnPrediction-vdb.xml, Contract_JDG_Module.zip, Screen Shot 2017-03-01 at 16.32.19.png, module pojo.xml, module.xml > > > SELECT * FROM Calls."Call" works as expected and returns all rows > Adding a where clause > SELECT * FROM Calls."Call" WHERE Calls."Call".Intlcalls > 0 > generate the following error: > org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidException: org.hibernate.hql.ParsingException: ISPN000402: The type com.redhat.demo.sko.pojo.Call has no property named 'Intlmins'. > Elapsed Time: 0 hr, 0 min, 0 sec, 191 ms. > If I join two VBL together and run the join query it returns the same error. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3653) Create examples for the following web data sources

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-3653?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-3653: ---------------------------------- Assignee: (was: Van Halbert) > Create examples for the following web data sources > -------------------------------------------------- > > Key: TEIID-3653 > URL: https://issues.jboss.org/browse/TEIID-3653 > Project: Teiid > Issue Type: Feature Request > Components: Quick Starts > Reporter: Van Halbert > Priority: Major > Fix For: Open To Community > > > Create examples for the following web data sources: > LinkedIn, Twitter, Facebook, Wikipedia, and Data.gov -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3653) Create examples for the following web data sources

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-3653?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3653: ------------------------------- Fix Version/s: Open To Community > Create examples for the following web data sources > -------------------------------------------------- > > Key: TEIID-3653 > URL: https://issues.jboss.org/browse/TEIID-3653 > Project: Teiid > Issue Type: Feature Request > Components: Quick Starts > Reporter: Van Halbert > Priority: Major > Fix For: Open To Community > > > Create examples for the following web data sources: > LinkedIn, Twitter, Facebook, Wikipedia, and Data.gov -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3693) Add data source support for reading documents (i.e., RTF, DOC, PDF)

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-3693?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-3693: ---------------------------------- Assignee: (was: Van Halbert) > Add data source support for reading documents (i.e., RTF, DOC, PDF) > ------------------------------------------------------------------- > > Key: TEIID-3693 > URL: https://issues.jboss.org/browse/TEIID-3693 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Van Halbert > Priority: Major > Fix For: Open To Community > > > Add data source support for reading documents (i.e., RTF, DOC, PDF). > From a runtime perspective the extraction logic is straight-forward when there is a parsing library. Here's one from CA using JSoup - https://github.com/rokhmanov/teiid-translators/blob/master/translator-scr... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3693) Add data source support for reading documents (i.e., RTF, DOC, PDF)

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-3693?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3693: ------------------------------- Fix Version/s: Open To Community > Add data source support for reading documents (i.e., RTF, DOC, PDF) > ------------------------------------------------------------------- > > Key: TEIID-3693 > URL: https://issues.jboss.org/browse/TEIID-3693 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > Fix For: Open To Community > > > Add data source support for reading documents (i.e., RTF, DOC, PDF). > From a runtime perspective the extraction logic is straight-forward when there is a parsing library. Here's one from CA using JSoup - https://github.com/rokhmanov/teiid-translators/blob/master/translator-scr... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4748) Provide translator/connector for calling Java api

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-4748?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-4748: ---------------------------------- Assignee: (was: Van Halbert) > Provide translator/connector for calling Java api > ------------------------------------------------- > > Key: TEIID-4748 > URL: https://issues.jboss.org/browse/TEIID-4748 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Van Halbert > Priority: Major > Fix For: Open To Community > > > Provide a translator/connector for doing the following: > - calling a java method on an API that returns an object (or collection) > - the return object should be exposed as a table > - the resource adapter should be able to provide the connection to the java api (either remote or local) > This scenario doesn't work with the current object translator, as its based on reading from a cache (map) and the connection methods are exposed based on that scenario. > The object translator has, at its core, the base for handling all the reflection logic for reading and writing on a java object. It may make sense to refactor out the core logic for reuse. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4792) Unable to use WHERE clause against a JDG data source - ISPN000402: The type com.redhat.demo.sko.pojo.Call has no property named .....

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-4792?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4792: ------------------------------------ As this issue is related to JDG 6, which has been removed upstream and is not recommended now that the hotrod support is in place for JDG 7. I would suggest this one changed to out-of-date. > Unable to use WHERE clause against a JDG data source - ISPN000402: The type com.redhat.demo.sko.pojo.Call has no property named ..... > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-4792 > URL: https://issues.jboss.org/browse/TEIID-4792 > Project: Teiid > Issue Type: Bug > Components: JDG Connector > Environment: Mac OS > JDV 6.3.4 > JDG 6.6.1 > JBDS 10.3.0 with JBDSIS 10.0.2 > Reporter: Cojan van Ballegooijen > Assignee: Van Halbert > Priority: Major > Attachments: Call_JDG_Module.zip, ChurnPrediction-vdb.xml, Contract_JDG_Module.zip, Screen Shot 2017-03-01 at 16.32.19.png, module pojo.xml, module.xml > > > SELECT * FROM Calls."Call" works as expected and returns all rows > Adding a where clause > SELECT * FROM Calls."Call" WHERE Calls."Call".Intlcalls > 0 > generate the following error: > org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidException: org.hibernate.hql.ParsingException: ISPN000402: The type com.redhat.demo.sko.pojo.Call has no property named 'Intlmins'. > Elapsed Time: 0 hr, 0 min, 0 sec, 191 ms. > If I join two VBL together and run the join query it returns the same error. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4695) Provide a better error with an invalid skipToken

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4695?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4695. ----------------------------------- Resolution: Done Added better exception message logic. We'll still allow though a skiptoken that has the right format even if it didn't come from the previous message. > Provide a better error with an invalid skipToken > ------------------------------------------------ > > Key: TEIID-4695 > URL: https://issues.jboss.org/browse/TEIID-4695 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 11.2 > > > The error message from an invalid skipToken could be improved - however users should not manually enter skipTokens. Similar errors still occur with our OData4 as the StringTokenizer used for the token will hit a no such element exception. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4534) Querying 1-to-many relationship in JDG data source may return the wrong results

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4534?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4534. ----------------------------------- Resolution: Out of Date Marking the upstream issue as out of date. > Querying 1-to-many relationship in JDG data source may return the wrong results > ------------------------------------------------------------------------------- > > Key: TEIID-4534 > URL: https://issues.jboss.org/browse/TEIID-4534 > Project: Teiid > Issue Type: Bug > Components: JDG Connector > Affects Versions: 8.12.x, 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > > When there is a 1-to-many relationship defined in a JDG schema, the results from querying the "many" relationship may return the wrong results. > Example: > Person --> Phone Numbers > INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567'); > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568'); > SELECT p.name, p.id, pn.number FROM Person p, PhoneNumber pn WHERE p.id=pn.id AND p.id=1 and number = '001234568' > or > Select * from PhoneNumber where number = '001234568' > return 2 rows, 1 for each phonenumber. > Why? Because JDG returns the Person object that meets those conditions. It doesn't filter the internal data to the Person object. Therefore, all phonenumbers are returned for the same person, generating a row for each. > This doesn't happen with 1-to-1 relationships because there's only ever 1 child object. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4534) Querying 1-to-many relationship in JDG data source may return the wrong results

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-4534?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4534: ------------------------------------ For upstream, this no longer applies, since support for JDG 6 has been removed. > Querying 1-to-many relationship in JDG data source may return the wrong results > ------------------------------------------------------------------------------- > > Key: TEIID-4534 > URL: https://issues.jboss.org/browse/TEIID-4534 > Project: Teiid > Issue Type: Bug > Components: JDG Connector > Affects Versions: 8.12.x, 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > > When there is a 1-to-many relationship defined in a JDG schema, the results from querying the "many" relationship may return the wrong results. > Example: > Person --> Phone Numbers > INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567'); > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568'); > SELECT p.name, p.id, pn.number FROM Person p, PhoneNumber pn WHERE p.id=pn.id AND p.id=1 and number = '001234568' > or > Select * from PhoneNumber where number = '001234568' > return 2 rows, 1 for each phonenumber. > Why? Because JDG returns the Person object that meets those conditions. It doesn't filter the internal data to the Person object. Therefore, all phonenumbers are returned for the same person, generating a row for each. > This doesn't happen with 1-to-1 relationships because there's only ever 1 child object. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2018