October 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-125) Provide source support Amazon Redshift

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-125?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-125: --------------------------------- Sprint: DV Sprint 54 > Provide source support Amazon Redshift > -------------------------------------- > > Key: TEIIDSB-125 > URL: https://issues.jboss.org/browse/TEIIDSB-125 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.0 > > > Provide translator support for Amazon Redshift -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-125) Provide source support Amazon Redshift

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-125?page=com.atlassian.jira.plugi... ] Ramesh Reddy reassigned TEIIDSB-125: ------------------------------------ Assignee: Ramesh Reddy > Provide source support Amazon Redshift > -------------------------------------- > > Key: TEIIDSB-125 > URL: https://issues.jboss.org/browse/TEIIDSB-125 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.0 > > > Provide translator support for Amazon Redshift -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-127) "No registered data sources found" if used "management.server.port=8081"

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-127?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIIDSB-127: -------------------------------------- [~i3draven] see if this works for you see https://github.com/teiid/teiid-spring-boot/pull/139 It is in the same technique as [~shawkins] saying with `DependesOn` but a way to do programmatically, little convoluted to find the data source specific beans, but works IMO. > "No registered data sources found" if used "management.server.port=8081" > ------------------------------------------------------------------------ > > Key: TEIIDSB-127 > URL: https://issues.jboss.org/browse/TEIIDSB-127 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource > Affects Versions: 1.2.0 > Environment: teiid-spring-boot > Reporter: Renat Eskenin > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.0 > > Attachments: TEIIDSB-127.zip > > > When we used management.server.port=8081 and server.port=8080 in spring boot properties we get exception > [2019-10-10 12:12:53,806 MSK] ERROR [test] org.teiid.PROCESSOR [restartedMain]: TEIID30019 Unexpected exception for request 8fPp+5AbzHhy.0 > java.lang.IllegalArgumentException: No registered data sources found > How can we change management port for spring actuator and do not broken Teiid? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5834) Class cast exception using web service with bind varables

by Mike Higgins (Jira)

Mike Higgins created TEIID-5834: ----------------------------------- Summary: Class cast exception using web service with bind varables Key: TEIID-5834 URL: https://issues.jboss.org/browse/TEIID-5834 Project: Teiid Issue Type: Bug Affects Versions: 11.1.2 Reporter: Mike Higgins Assignee: Steven Hawkins I am using a restful web service, which works fine if literal values are used to constrain it. However, when I use bind variables, it gives me a traceback: java.lang.ClassCastException: org.teiid.query.sql.lang.ImmutableCompareCriteria cannot be cast to org.teiid.query.sql.lang.AbstractSetCriteria at org.teiid.query.processor.relational.DependentCriteriaProcessor.prepareCriteria(DependentCriteriaProcessor.java:352) at org.teiid.query.processor.relational.DependentProcedureCriteriaProcessor.prepareNextCommand(DependentProcedureCriteriaProcessor.java:60) at org.teiid.query.processor.relational.DependentProcedureExecutionNode.prepareNextCommand(DependentProcedureExecutionNode.java:88) at org.teiid.query.processor.relational.PlanExecutionNode.open(PlanExecutionNode.java:79) at org.teiid.query.processor.relational.DependentProcedureExecutionNode.open(DependentProcedureExecutionNode.java:108) at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) at org.teiid.query.processor.relational.JoinStrategy.openRight(JoinStrategy.java:101) at org.teiid.query.processor.relational.JoinNode.nextBatchDirectInternal(JoinNode.java:256) at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:200) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277) at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277) at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:141) at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:148) at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:111) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:160) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:142) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:492) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:362) ... 8 more The SQL is: SELECT CAIMANM.LM_BIOLOGICAL_SYSTEM."BIOLOGICAL_SYSTEM_UID", WS_CLUSTER.WS_CLUSTER_T."VH_SPECIES", WS_CLUSTER.WS_CLUSTER_T."PROJECT_SHORT_NAME", WS_CLUSTER.WS_CLUSTER_T."biosysid" FROM caimanm.lm_biological_system LEFT OUTER JOIN WS_cluster.WS_cluster_t ON (CAIMANM.LM_BIOLOGICAL_SYSTEM."BIOLOGICAL_SYSTEM_UID" = WS_CLUSTER.WS_CLUSTER_T."biosysid") AND (WS_CLUSTER.WS_CLUSTER_T."biosysid" in (?, ?, ?)) WHERE (CAIMANM.LM_BIOLOGICAL_SYSTEM."BIOLOGICAL_SYSTEM_UID" in (?, ?, ?)) Where WS_CLUSTER is the web service. I didn't find any issues about this so I was not sure if a later version would work. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5826) Odata based translators ignore column metadata from source during metadata import

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5826?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-5826. --------------------------------- Resolution: Done Updated the metadata resolution to look at precision, scale, length and default value options. Also corrected the issue when applying to timestamp, the precision is used as scale. > Odata based translators ignore column metadata from source during metadata import > --------------------------------------------------------------------------------- > > Key: TEIID-5826 > URL: https://issues.jboss.org/browse/TEIID-5826 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 13.0 > > > The OData V2 and SAP and OData V4 translators do not set column metadata such as precision and scale and length the is supplied to it through $metadata call on to the schema it builds on Teiid. Then Teiid assumes some of the defaults. > This can be fixed by setting the values to what has been delivered as part of metadata. Example here https://github.com/rareddy/sap-demo/blob/master/src/main/java/org/teiid/t... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5833) Update extension metadata uri's

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5833?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-5833 at 10/25/19 2:30 PM: ----------------------------------------------------------------- In more detail: * "set namespace" will throw an exception. Anyone using a custom namespace will need to choose a consistent name/prefix across all usage. The fix in most cases is just to remove the set namespace statement and replace the prefix usage with the uri. If they choose to go with something other than the uri, then that may require changes in custom translators and other sql. * deprecate AbstractMetadataRecord.getProperty(String key, boolean checkUnqualified). The new getProperty will look for teiid_ properties by both prefix and fqn for backwards compatibility. * change all of our built-in lookups (mostly in translators) to just use the prefix name * sys.properties will report teiid_ properties by both the prefix and uri. was (Author: shawkins): In more detail: * * "set namespace" will throw an exception. Anyone using a custom namespace will need to choose a consistent name/prefix across all usage. The fix in most cases is just to remove the set namespace statement. * deprecate AbstractMetadataRecord.getProperty(String key, boolean checkUnqualified) * change all of our built-in lookups (mostly in translators) to just use the prefix name The only big breaking change is for custom translator development that were using uri fqn references to get properties. This will require a code change on their end. > Update extension metadata uri's > ------------------------------- > > Key: TEIID-5833 > URL: https://issues.jboss.org/browse/TEIID-5833 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > There are a lot of long/old extension metadata uris - including the odata one which still references teiid designer. We should see about making these simpler - perhaps even dropping the notion of fqn vs prefix altogether so that we just deal with the raw prefixes. > The only issue with changes is when the extension properties are left fully qualified in the metadata. We'd need to lookup under both the old and new versions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-39) Create launcher for delivery on https://launch.openshift.io/launch/

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-39?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIIDSB-39: ----------------------------------- Assignee: (was: Ramesh Reddy) > Create launcher for delivery on https://launch.openshift.io/launch/ > ------------------------------------------------------------------- > > Key: TEIIDSB-39 > URL: https://issues.jboss.org/browse/TEIIDSB-39 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: OpenShift > Reporter: Van Halbert > Priority: Major > > Create a launcher that will enable it to be used here https://launch.openshift.io/launch/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2819) Use Oauth SAML Bearer Assertion Flow

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-2819?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2819. --------------------------------- Resolution: Out of Date > Use Oauth SAML Bearer Assertion Flow > ------------------------------------ > > Key: TEIID-2819 > URL: https://issues.jboss.org/browse/TEIID-2819 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Major > Fix For: 13.x > > > I can secure my mobile and cloud applications? > Consider doing SAML first and Oauth later – the use cases are the same, the implementation is different > Link - https://help.salesforce.com/apex/HTViewHelpDoc?id=remoteaccess_oauth_SAML... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3590) Provide $search extension to the OData V4 in Teiid

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-3590?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3590: ----------------------------------- Assignee: (was: Ramesh Reddy) > Provide $search extension to the OData V4 in Teiid > -------------------------------------------------- > > Key: TEIID-3590 > URL: https://issues.jboss.org/browse/TEIID-3590 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.11 > Reporter: Tom Johnston > Priority: Major > Fix For: 13.x > > > http://www.odata.org/getting-started/basic-tutorial/#select > > I am trying the following > > http://127.0.0.1:8080/odata/VDB1/Client1010_026V.Client_Check_History/?$s... > > It seems to return ALL data and disregard the ?$search= (which in this case I'd expect none) > > are there only portions of the odata protocol implemented?... or am I misunderstanding the odata.org link information -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-127) "No registered data sources found" if used "management.server.port=8081"

by Renat Eskenin (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-127?page=com.atlassian.jira.plugi... ] Renat Eskenin commented on TEIIDSB-127: --------------------------------------- May be need to add new requered property with list of datasources names and its priority's? > "No registered data sources found" if used "management.server.port=8081" > ------------------------------------------------------------------------ > > Key: TEIIDSB-127 > URL: https://issues.jboss.org/browse/TEIIDSB-127 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource > Affects Versions: 1.2.0 > Environment: teiid-spring-boot > Reporter: Renat Eskenin > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.0 > > Attachments: TEIIDSB-127.zip > > > When we used management.server.port=8081 and server.port=8080 in spring boot properties we get exception > [2019-10-10 12:12:53,806 MSK] ERROR [test] org.teiid.PROCESSOR [restartedMain]: TEIID30019 Unexpected exception for request 8fPp+5AbzHhy.0 > java.lang.IllegalArgumentException: No registered data sources found > How can we change management port for spring actuator and do not broken Teiid? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2019