[JBoss JIRA] (TEIIDSB-148) Dependency conflict, need to align wsdl4j with version coming from teiid
by Van Halbert (Jira)
Van Halbert created TEIIDSB-148:
-----------------------------------
Summary: Dependency conflict, need to align wsdl4j with version coming from teiid
Key: TEIIDSB-148
URL: https://issues.redhat.com/browse/TEIIDSB-148
Project: Teiid Spring Boot
Issue Type: Bug
Components: core
Affects Versions: 1.3.0
Reporter: Van Halbert
Assignee: Van Halbert
Dependency alignment issue with the teiid version from the translator-ws:
{code}
<groupId>wsdl4j</groupId>
<artifactId>wsdl4j</artifactId>
<version>1.6.3.redhat-2</version>
{code}
teiid-spring-boot tries to align with 1.6.3.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIID-5818) separate the wildfly build/repo
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5818?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on TEIID-5818:
---------------------------------------
After running the release, I realized that we still need to reference the wildfly module in the release and final-release profiles as well. core-release will still exclude wildfly.
> separate the wildfly build/repo
> -------------------------------
>
> Key: TEIID-5818
> URL: https://issues.redhat.com/browse/TEIID-5818
> Project: Teiid
> Issue Type: Task
> Components: Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0
>
>
> The wildfly build should be further decoupled from the Teiid build. Initially this could be as simple as removing the module references from the parent pom. We also need to update the wildfly logic poms to start referencing teiid artifacts via a distinct version (rather than project.version).
> From there we can decide how to promote it into its own repository. As it doesn't seem likely that we'll invest in a mechanism to update teiid-wildly using some kind of teiid core overlay, we'll likely just do a teiid-wildfly release with every teiid release.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIID-5865) Odata $expand does not work
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5865?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on TEIID-5865:
---------------------------------------
This affects sources that support array_agg - the resulting array value is not being converted to a value that the engine can handle. This seems to be particular to multi-dimensional arrays - which are created in this case by a pushdown query like SELECT ARRAY_AGG((col, col..) ...
The engine logic works only seems to work if a raw two dimensional array is given to it. This will affect the translators that are marked as supporting array_agg and the array type, so pg, teiid, and couchbase.
A workaround is to disable array_agg support on the translator.
> Odata $expand does not work
> ---------------------------
>
> Key: TEIID-5865
> URL: https://issues.redhat.com/browse/TEIID-5865
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 12.3
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
>
> When I try the following query using customer-dv deployment against postgresql
> https://rdbms-springboot-dv-demo.apps.cluster-london-966d.london-966d.ope...
> I get the following error:
> {"error":{"code":"TEIID30504","message":"TEIID30504 sampledb: TEIID31176 Could not convert source column v_0.c_1 AS c_3 to the expected runtime type object[][]"}}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years