[JBoss JIRA] (TEIID-4954) The type ispn2.G2 has no property named 'e1'.
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4954?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-4954.
---------------------------------
Resolution: Duplicate Issue
> The type ispn2.G2 has no property named 'e1'.
> ---------------------------------------------
>
> Key: TEIID-4954
> URL: https://issues.jboss.org/browse/TEIID-4954
> Project: Teiid
> Issue Type: Bug
> Components: Infinispan
> Affects Versions: 10.0
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Blocker
> Attachments: jdg-remote-cache-ddl-vdb.xml
>
>
> When using the attached VDB, where G1 and G2 look similar, get the following error:
> 09:34:37,202 ERROR [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue22) BA7GA3WbC1fa Connector worker process failed for atomic-request=BA7GA3WbC1fa.7.3.1: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=10 returned server error (status=0x85): org.infinispan.objectfilter.ParsingException: ISPN028501: The type ispn2.G2 has no property named 'e1'.
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:363)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:152)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:138)
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:60)
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:68)
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:30)
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:56)
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.executeQuery(RemoteQuery.java:68)
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.list(RemoteQuery.java:53)
> at https://issues.jboss.org/browse/TEIID-4948org.teiid.translator.infinispan...
> at org.teiid.translator.infinispan.hotrod.InfinispanResponse.getNextRow(InfinispanResponse.java:86)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (TEIID-4947) Error with Salesforce translator if criteria on outer join on a custom table is from the right side table
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIID-4947?page=com.atlassian.jira.plugin... ]
Johnathon Lee updated TEIID-4947:
---------------------------------
Fix Version/s: 8.12.12.6_3
> Error with Salesforce translator if criteria on outer join on a custom table is from the right side table
> ----------------------------------------------------------------------------------------------------------
>
> Key: TEIID-4947
> URL: https://issues.jboss.org/browse/TEIID-4947
> Project: Teiid
> Issue Type: Bug
> Components: Salesforce Connector
> Affects Versions: 8.7.11.6_2, 8.12.10.6_3
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 10.0, 9.3.1, 8.12.12.6_3
>
>
> Running a left outer join between a parent and child custom table in salesforce results in an error:
> select a.id, a.name, a.LastModifiedDate, b.Order_Recipe_Steps__c, b.name
> from MPRS_Salesforce.Media_Prep_Order_Recipe_Steps__c a left outer join "MPRS_Salesforce"."Recipe_Step_Detail__c" b
> on (a.id = b.Order_Recipe_Steps__c)
> where b.LastModifiedDate >= parsetimestamp('2016-05-04 15:01:03.0', 'yyyy-MM-dd hh:mm:ss.s')
> Error: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 MPRS_Salesforce: com.sforce.soap.partner.InvalidSObjectFault: INVALID_TYPE:
> Recipe_Step_Detail__c.Catalog_Item__c FROM Recipe_Step_Detail__cs) FROM Media_Prep_Order_Recipe_Steps__c
> ^
> ERROR at Row:1:Column:1137
> Didn't understand relationship 'Recipe_Step_Detail__cs' in FROM part of query call. If you are attempting to use a custom relationship, be sure to append the '__r' after the custom relationship name. Please reference your WSDL or the describe call for the appropriate names.
> SQLState: 50000
> ErrorCode: 30504
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (TEIID-4867) Loosen up OData4 URL validation or parsing
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4867?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4867.
-----------------------------------
Resolution: Done
> Loosen up OData4 URL validation or parsing
> ------------------------------------------
>
> Key: TEIID-4867
> URL: https://issues.jboss.org/browse/TEIID-4867
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.12.8.6_3
> Environment: JDV 6.3.2
> Windows 7
> Reporter: Steve Tran
> Assignee: Johnathon Lee
> Fix For: 8.12.x-6.4, 8.12.11.6_3
>
>
> I'm accessing my JDV table via OData4 through Salesforce's UI builder. The salesforce engine itself is creating the OData calls, and whenever a $filter is needed with multiple columns, it looks like salesforce pads the column name with a space in front and behind. That'll make the URL look like ...$filter={color:red}%20{color}ColumnA{color:red}%20{color}eq%20123%20and{color:red}%20{color}ColumnB{color:red}%20{color}eq...
> The first space right after the $filter= throws off the JDV engine as it thinks it's a malformed URL - which I guess it is. The thing is when I tested it via the OData2 interface, it accepted it just fine. I'm not sure if the OData4 specifications explicitly state in terms of the URL, so it could be anybody's bug. Perhaps we could make JDV a little more forgiving and trim the spaces after un-URL-encoding the URI.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (TEIID-4981) Support Amazon S3 Transaltor
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-4981:
-----------------------------------
Summary: Support Amazon S3 Transaltor
Key: TEIID-4981
URL: https://issues.jboss.org/browse/TEIID-4981
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Ramesh Reddy
Fix For: Open To Community
Support Amazon S3 access from Teiid. Typically this is viewed as file-based access? however handling the security is key here.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (TEIID-4957) Setting Connection Type on VDB of a Domain Managed server gets set back to default after server restart
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4957?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4957:
-------------------------------------
[~jolee] I do not have a solution yet for this, the simple workaround is to edit the vdb.xml and add the necessary changes manually.
> Setting Connection Type on VDB of a Domain Managed server gets set back to default after server restart
> -------------------------------------------------------------------------------------------------------
>
> Key: TEIID-4957
> URL: https://issues.jboss.org/browse/TEIID-4957
> Project: Teiid
> Issue Type: Bug
> Components: VDB
> Affects Versions: 8.12.10.6_3
> Reporter: Debbie Steigner
> Assignee: Ramesh Reddy
> Fix For: 10.0
>
>
> After deploying a VDB to a managed server group, set the Connection type to anything but the default of By_Version, so None or Any. Now restart the server and you'll see the Connection type is reset to the default.
> What I see is that when the change is made a vdb.xml with that new connection-type is written to the /DVserverhome/domain/servers/server-two/data/teiid-data/SampleVDB_1 folder, this folder is deleted upon a restart though so the change is not kept.
> This only happens in Domain mode, running in Standalone mode saves the change because the teiid-data is not deleted on a restart.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (TEIID-4969) Couchbase - ORDER BY returns empty result
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4969?page=com.atlassian.jira.plugin... ]
Work on TEIID-4969 started by Steven Hawkins.
---------------------------------------------
> Couchbase - ORDER BY returns empty result
> -----------------------------------------
>
> Key: TEIID-4969
> URL: https://issues.jboss.org/browse/TEIID-4969
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.x-6.4
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Priority: Blocker
>
> Issuing query like \[1\] returns empty result. From what I can see, query seems to not be properly translated to the source-specific query \[2\].
> {code:sql|title=\[1\] Query}
> SELECT IntKey AS Total FROM BQT1.SmallA ORDER BY IntKey
> {code}
> {code:plain|title=\[2\] Source-specific query - c_0 is not defined anywhere}
> 09:40:11,748 DEBUG [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue60) TEIID29001 Source-specific Query: SELECT `$cb_c1_IntKey` FROM `dvqe_small` `$cb_t1` LET `$cb_c1_IntKey` = `$cb_t1`.`IntKey`c_0 WHERE `$cb_t1`.`type` = 'SmallA' ORDER BY c_0
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months