[JBoss JIRA] (TEIID-5589) NavigationProperty not working with Teiid odata, results in TEIID16053
by Christoph John (Jira)
[ https://issues.jboss.org/browse/TEIID-5589?page=com.atlassian.jira.plugin... ]
Christoph John updated TEIID-5589:
----------------------------------
Description:
Teiid throws an error in case it tries to follow an odata Navigation property. I tried this by using $expand and also by directly following a path. Two examples are shown below. My $metaddata.xml file is attached, and also a single record from the Account table in which the relevant comparison seems to happen. the uuidUser property you can find here.
I do not understand the error message. What is not clear to me is the assignment which is mentioned there g1.uuidUser = g0.fkProfile
Just for your awareness, uuidUser and fkProfile are different columns of different types that should not be compared in anyway. Maybe this is a hint what is going wrong. I would the relevant NavigationProperty expect to be
<NavigationProperty Name="fkProfileInProfile" Type="my_nutri_diary.Account" Nullable="false">
<ReferentialConstraint Property="fkProfile" ReferencedProperty="idProfile"/>
Here are two example queries which fail with the same error
http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)?$expand=fkPro...
http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)/fkProfileInPr...
<error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
<code>TEIID31172</code>
<message>
TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
</message>
</error>
----------------------
There might also exist a bug in Teiid Designer, when changing the private key and reimporting the database, the source in Teiid Designer looks as expected. However, a sync of the vdb seems not to work properly. For the workaround described in this ticket, I had to create a new vdb in order to get things to work correctely.
was:
Teiid throws an error in case it tries to follow an odata Navigation property. I tried this by using $expand and also by directly following a path. Two examples are shown below. My $metaddata.xml file is attached, and also a single record from the Account table in which the relevant comparison seems to happen. the uuidUser property you can find here.
I do not understand the error message. What is not clear to me is the assignment which is mentioned there g1.uuidUser = g0.fkProfile
Just for your awareness, uuidUser and fkProfile are different columns of different types that should not be compared in anyway. Maybe this is a hint what is going wrong. I would the relevant NavigationProperty expect to be
<NavigationProperty Name="fkProfileInProfile" Type="my_nutri_diary.Account" Nullable="false">
<ReferentialConstraint Property="fkProfile" ReferencedProperty="idProfile"/>
Here are two example queries which fail with the same error
http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)?$expand=fkPro...
http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)/fkProfileInPr...
<error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
<code>TEIID31172</code>
<message>
TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
</message>
</error>
----------------------------
-Update 9.1.19: I need to to add here, that there might be a second bug involved into the observation. It seems, that the error is due to type comparisons. As there was a comparison with Account.uuuiUser in the error message and as my table Account just holds a one to one mapping between uuids and integers which represent database internal IDs, I switched the primary key in the Account table from uuidUser to idProfile in hope to circumvent the bug.
So my new observation is, when I disable row constraints in which I must have a comparison against uuidUser in the form "Profile.fkProfile in (SELECT Account.idProfile FROM Account WHERE Account.uuidUser = LEFT(user(), 36))" and switch hte primary key as mention previously, than I can follow the navigation property. However, as soon as I enable row constraints again I get a similar error message as before:--
<error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
<code>TEIID31172</code>
<message>
TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
</message>
</error>
As I am not sure if the issue derives from the same place in code, I thought I should add this here.-
> NavigationProperty not working with Teiid odata, results in TEIID16053
> ------------------------------------------------------------------------
>
> Key: TEIID-5589
> URL: https://issues.jboss.org/browse/TEIID-5589
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 11.2.1
> Reporter: Christoph John
> Assignee: Steven Hawkins
> Priority: Major
> Attachments: AccountRecord.xml, metadata.xml
>
>
> Teiid throws an error in case it tries to follow an odata Navigation property. I tried this by using $expand and also by directly following a path. Two examples are shown below. My $metaddata.xml file is attached, and also a single record from the Account table in which the relevant comparison seems to happen. the uuidUser property you can find here.
> I do not understand the error message. What is not clear to me is the assignment which is mentioned there g1.uuidUser = g0.fkProfile
> Just for your awareness, uuidUser and fkProfile are different columns of different types that should not be compared in anyway. Maybe this is a hint what is going wrong. I would the relevant NavigationProperty expect to be
> <NavigationProperty Name="fkProfileInProfile" Type="my_nutri_diary.Account" Nullable="false">
> <ReferentialConstraint Property="fkProfile" ReferencedProperty="idProfile"/>
> Here are two example queries which fail with the same error
> http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)?$expand=fkPro...
> http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)/fkProfileInPr...
> <error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
> <code>TEIID31172</code>
> <message>
> TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
> </message>
> </error>
> ----------------------
> There might also exist a bug in Teiid Designer, when changing the private key and reimporting the database, the source in Teiid Designer looks as expected. However, a sync of the vdb seems not to work properly. For the workaround described in this ticket, I had to create a new vdb in order to get things to work correctely.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (TEIID-5589) NavigationProperty not working with Teiid odata, results in TEIID16053
by Christoph John (Jira)
[ https://issues.jboss.org/browse/TEIID-5589?page=com.atlassian.jira.plugin... ]
Christoph John updated TEIID-5589:
----------------------------------
Description:
Teiid throws an error in case it tries to follow an odata Navigation property. I tried this by using $expand and also by directly following a path. Two examples are shown below. My $metaddata.xml file is attached, and also a single record from the Account table in which the relevant comparison seems to happen. the uuidUser property you can find here.
I do not understand the error message. What is not clear to me is the assignment which is mentioned there g1.uuidUser = g0.fkProfile
Just for your awareness, uuidUser and fkProfile are different columns of different types that should not be compared in anyway. Maybe this is a hint what is going wrong. I would the relevant NavigationProperty expect to be
<NavigationProperty Name="fkProfileInProfile" Type="my_nutri_diary.Account" Nullable="false">
<ReferentialConstraint Property="fkProfile" ReferencedProperty="idProfile"/>
Here are two example queries which fail with the same error
http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)?$expand=fkPro...
http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)/fkProfileInPr...
<error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
<code>TEIID31172</code>
<message>
TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
</message>
</error>
----------------------------
-Update 9.1.19: I need to to add here, that there might be a second bug involved into the observation. It seems, that the error is due to type comparisons. As there was a comparison with Account.uuuiUser in the error message and as my table Account just holds a one to one mapping between uuids and integers which represent database internal IDs, I switched the primary key in the Account table from uuidUser to idProfile in hope to circumvent the bug.
So my new observation is, when I disable row constraints in which I must have a comparison against uuidUser in the form "Profile.fkProfile in (SELECT Account.idProfile FROM Account WHERE Account.uuidUser = LEFT(user(), 36))" and switch hte primary key as mention previously, than I can follow the navigation property. However, as soon as I enable row constraints again I get a similar error message as before:--
<error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
<code>TEIID31172</code>
<message>
TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
</message>
</error>
As I am not sure if the issue derives from the same place in code, I thought I should add this here.-
was:
Teiid throws an error in case it tries to follow an odata Navigation property. I tried this by using $expand and also by directly following a path. Two examples are shown below. My $metaddata.xml file is attached, and also a single record from the Account table in which the relevant comparison seems to happen. the uuidUser property you can find here.
I do not understand the error message. What is not clear to me is the assignment which is mentioned there g1.uuidUser = g0.fkProfile
Just for your awareness, uuidUser and fkProfile are different columns of different types that should not be compared in anyway. Maybe this is a hint what is going wrong. I would the relevant NavigationProperty expect to be
<NavigationProperty Name="fkProfileInProfile" Type="my_nutri_diary.Account" Nullable="false">
<ReferentialConstraint Property="fkProfile" ReferencedProperty="idProfile"/>
Here are two example queries which fail with the same error
http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)?$expand=fkPro...
http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)/fkProfileInPr...
<error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
<code>TEIID31172</code>
<message>
TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
</message>
</error>
----------------------------
Update 9.1.19: I need to to add here, that there might be a second bug involved into the observation. It seems, that the error is due to type comparisons. As there was a comparison with Account.uuuiUser in the error message and as my table Account just holds a one to one mapping between uuids and integers which represent database internal IDs, I switched the primary key in the Account table from uuidUser to idProfile in hope to circumvent the bug.
So my new observation is, when I disable row constraints in which I must have a comparison against uuidUser in the form "Profile.fkProfile in (SELECT Account.idProfile FROM Account WHERE Account.uuidUser = LEFT(user(), 36))" and switch hte primary key as mention previously, than I can follow the navigation property. However, as soon as I enable row constraints again I get a similar error message as before:
<error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
<code>TEIID31172</code>
<message>
TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
</message>
</error>
As I am not sure if the issue derives from the same place in code, I thought I should add this here.
> NavigationProperty not working with Teiid odata, results in TEIID16053
> ------------------------------------------------------------------------
>
> Key: TEIID-5589
> URL: https://issues.jboss.org/browse/TEIID-5589
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 11.2.1
> Reporter: Christoph John
> Assignee: Steven Hawkins
> Priority: Major
> Attachments: AccountRecord.xml, metadata.xml
>
>
> Teiid throws an error in case it tries to follow an odata Navigation property. I tried this by using $expand and also by directly following a path. Two examples are shown below. My $metaddata.xml file is attached, and also a single record from the Account table in which the relevant comparison seems to happen. the uuidUser property you can find here.
> I do not understand the error message. What is not clear to me is the assignment which is mentioned there g1.uuidUser = g0.fkProfile
> Just for your awareness, uuidUser and fkProfile are different columns of different types that should not be compared in anyway. Maybe this is a hint what is going wrong. I would the relevant NavigationProperty expect to be
> <NavigationProperty Name="fkProfileInProfile" Type="my_nutri_diary.Account" Nullable="false">
> <ReferentialConstraint Property="fkProfile" ReferencedProperty="idProfile"/>
> Here are two example queries which fail with the same error
> http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)?$expand=fkPro...
> http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)/fkProfileInPr...
> <error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
> <code>TEIID31172</code>
> <message>
> TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
> </message>
> </error>
> ----------------------------
> -Update 9.1.19: I need to to add here, that there might be a second bug involved into the observation. It seems, that the error is due to type comparisons. As there was a comparison with Account.uuuiUser in the error message and as my table Account just holds a one to one mapping between uuids and integers which represent database internal IDs, I switched the primary key in the Account table from uuidUser to idProfile in hope to circumvent the bug.
> So my new observation is, when I disable row constraints in which I must have a comparison against uuidUser in the form "Profile.fkProfile in (SELECT Account.idProfile FROM Account WHERE Account.uuidUser = LEFT(user(), 36))" and switch hte primary key as mention previously, than I can follow the navigation property. However, as soon as I enable row constraints again I get a similar error message as before:--
> <error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
> <code>TEIID31172</code>
> <message>
> TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
> </message>
> </error>
> As I am not sure if the issue derives from the same place in code, I thought I should add this here.-
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (TEIID-5521) Add build plugins used by basepom to help with dependency handling
by Van Halbert (Jira)
[ https://issues.jboss.org/browse/TEIID-5521?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-5521:
------------------------------------
Just an FYI, that the change in bom parent now doesn't like the subprojects using exclusions in their poms. Those exclusions need to be moved out the the root pom. I've run into this twice now in translators.
> Add build plugins used by basepom to help with dependency handling
> ------------------------------------------------------------------
>
> Key: TEIID-5521
> URL: https://issues.jboss.org/browse/TEIID-5521
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Affects Versions: 12.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Major
> Fix For: 12.1
>
>
> Utilize plugins that basebom uses, which will help reduce half the headaches you go though during the productization with versions.
> plugins:
> * duplicate-finder-maven-plugin
> * maven-dependency-plugin
> * maven-dependency-versions-check-plugin
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (TEIID-5587) Oracle 11 drivers don't accept NVARCHAR type
by RH Bugzilla Integration (Jira)
[ https://issues.jboss.org/browse/TEIID-5587?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-5587:
------------------------------------------------
jolee(a)redhat.com changed the Status of [bug 1664723|https://bugzilla.redhat.com/show_bug.cgi?id=1664723] from NEW to CLOSED
> Oracle 11 drivers don't accept NVARCHAR type
> --------------------------------------------
>
> Key: TEIID-5587
> URL: https://issues.jboss.org/browse/TEIID-5587
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.0, 11.2.2
>
>
> Older oracle drivers, such as 11.2.0.1.0 do not accept the sql type NVARCHAR as an argument to set object, which results in an exception like:
> {code}
> Caused by: java.sql.SQLException: Invalid column type
> at oracle.jdbc.driver.OraclePreparedStatement.setObjectCritical(OraclePreparedStatement.java:12187)
> at oracle.jdbc.driver.OraclePreparedStatement.setObjectInternal(OraclePreparedStatement.java:11577)
> at oracle.jdbc.driver.OraclePreparedStatement.setObject(OraclePreparedStatement.java:12286)
> at oracle.jdbc.driver.OraclePreparedStatementWrapper.setObject(OraclePreparedStatementWrapper.java:548)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.bindValue(JDBCExecutionFactory.java:1145)
> {code}
> We can also safely narrow our usage of the n types with oracle as anything in the latin 1 supplement is still allowed in varchar values.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (TEIID-5589) NavigationProperty not working with Teiid odata, results in TEIID16053
by Christoph John (Jira)
[ https://issues.jboss.org/browse/TEIID-5589?page=com.atlassian.jira.plugin... ]
Christoph John updated TEIID-5589:
----------------------------------
Priority: Major (was: Blocker)
> NavigationProperty not working with Teiid odata, results in TEIID16053
> ------------------------------------------------------------------------
>
> Key: TEIID-5589
> URL: https://issues.jboss.org/browse/TEIID-5589
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 11.2.1
> Reporter: Christoph John
> Assignee: Steven Hawkins
> Priority: Major
> Attachments: AccountRecord.xml, metadata.xml
>
>
> Teiid throws an error in case it tries to follow an odata Navigation property. I tried this by using $expand and also by directly following a path. Two examples are shown below. My $metaddata.xml file is attached, and also a single record from the Account table in which the relevant comparison seems to happen. the uuidUser property you can find here.
> I do not understand the error message. What is not clear to me is the assignment which is mentioned there g1.uuidUser = g0.fkProfile
> Just for your awareness, uuidUser and fkProfile are different columns of different types that should not be compared in anyway. Maybe this is a hint what is going wrong. I would the relevant NavigationProperty expect to be
> <NavigationProperty Name="fkProfileInProfile" Type="my_nutri_diary.Account" Nullable="false">
> <ReferentialConstraint Property="fkProfile" ReferencedProperty="idProfile"/>
> Here are two example queries which fail with the same error
> http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)?$expand=fkPro...
> http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)/fkProfileInPr...
> <error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
> <code>TEIID31172</code>
> <message>
> TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
> </message>
> </error>
> ----------------------------
> Update 9.1.19: I need to to add here, that there might be a second bug involved into the observation. It seems, that the error is due to type comparisons. As there was a comparison with Account.uuuiUser in the error message and as my table Account just holds a one to one mapping between uuids and integers which represent database internal IDs, I switched the primary key in the Account table from uuidUser to idProfile in hope to circumvent the bug.
> So my new observation is, when I disable row constraints in which I must have a comparison against uuidUser in the form "Profile.fkProfile in (SELECT Account.idProfile FROM Account WHERE Account.uuidUser = LEFT(user(), 36))" and switch hte primary key as mention previously, than I can follow the navigation property. However, as soon as I enable row constraints again I get a similar error message as before:
> <error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
> <code>TEIID31172</code>
> <message>
> TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
> </message>
> </error>
> As I am not sure if the issue derives from the same place in code, I thought I should add this here.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (TEIID-5589) NavigationProperty not working with Teiid odata, results in TEIID16053
by Christoph John (Jira)
[ https://issues.jboss.org/browse/TEIID-5589?page=com.atlassian.jira.plugin... ]
Christoph John updated TEIID-5589:
----------------------------------
Workaround Description:
No general workaround found yet. However, what is working for me is to change the primary key from a string value to an integer. I could fortunately do this, as I have a special situation with a table which holds uuids mapped to their internal database counterparts which are IDs of type integer. Hence, in my case both columns qualify as primary keys.
Note, when using Teiid Designer it was not sufficient for me to reimport the database source and sync the vdb. I had to create and configure an entirely new vdb to get things working. Might be that I hit another issue here with Teiid Designer.
was:No general workaround found yet. However, what is working for me is to change the primary key from a string value to an integer. I could do this as I have a table with a special case in which uuid are mapped to their internal database counterparts which are IDs of type integer. Note, when using Teiid Designer it was not sufficient for me to to reimport the database source and sync the vdb. I had to create and configure an entirely new vdb to get things working. Might be that I hit another issue here with Teiid Designer.
> NavigationProperty not working with Teiid odata, results in TEIID16053
> ------------------------------------------------------------------------
>
> Key: TEIID-5589
> URL: https://issues.jboss.org/browse/TEIID-5589
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 11.2.1
> Reporter: Christoph John
> Assignee: Steven Hawkins
> Priority: Blocker
> Attachments: AccountRecord.xml, metadata.xml
>
>
> Teiid throws an error in case it tries to follow an odata Navigation property. I tried this by using $expand and also by directly following a path. Two examples are shown below. My $metaddata.xml file is attached, and also a single record from the Account table in which the relevant comparison seems to happen. the uuidUser property you can find here.
> I do not understand the error message. What is not clear to me is the assignment which is mentioned there g1.uuidUser = g0.fkProfile
> Just for your awareness, uuidUser and fkProfile are different columns of different types that should not be compared in anyway. Maybe this is a hint what is going wrong. I would the relevant NavigationProperty expect to be
> <NavigationProperty Name="fkProfileInProfile" Type="my_nutri_diary.Account" Nullable="false">
> <ReferentialConstraint Property="fkProfile" ReferencedProperty="idProfile"/>
> Here are two example queries which fail with the same error
> http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)?$expand=fkPro...
> http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)/fkProfileInPr...
> <error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
> <code>TEIID31172</code>
> <message>
> TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
> </message>
> </error>
> ----------------------------
> Update 9.1.19: I need to to add here, that there might be a second bug involved into the observation. It seems, that the error is due to type comparisons. As there was a comparison with Account.uuuiUser in the error message and as my table Account just holds a one to one mapping between uuids and integers which represent database internal IDs, I switched the primary key in the Account table from uuidUser to idProfile in hope to circumvent the bug.
> So my new observation is, when I disable row constraints in which I must have a comparison against uuidUser in the form "Profile.fkProfile in (SELECT Account.idProfile FROM Account WHERE Account.uuidUser = LEFT(user(), 36))" and switch hte primary key as mention previously, than I can follow the navigation property. However, as soon as I enable row constraints again I get a similar error message as before:
> <error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
> <code>TEIID31172</code>
> <message>
> TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
> </message>
> </error>
> As I am not sure if the issue derives from the same place in code, I thought I should add this here.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (TEIID-5589) NavigationProperty not working with Teiid odata, results in TEIID16053
by Christoph John (Jira)
[ https://issues.jboss.org/browse/TEIID-5589?page=com.atlassian.jira.plugin... ]
Christoph John updated TEIID-5589:
----------------------------------
Workaround Description: No general workaround found yet. However, what is working for me is to change the primary key from a string value to an integer. I could do this as I have a table with a special case in which uuid are mapped to their internal database counterparts which are IDs of type integer. Note, when using Teiid Designer it was not sufficient for me to to reimport the database source and sync the vdb. I had to create and configure an entirely new vdb to get things working. Might be that I hit another issue here with Teiid Designer. (was: No workaround found yet)
> NavigationProperty not working with Teiid odata, results in TEIID16053
> ------------------------------------------------------------------------
>
> Key: TEIID-5589
> URL: https://issues.jboss.org/browse/TEIID-5589
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 11.2.1
> Reporter: Christoph John
> Assignee: Steven Hawkins
> Priority: Blocker
> Attachments: AccountRecord.xml, metadata.xml
>
>
> Teiid throws an error in case it tries to follow an odata Navigation property. I tried this by using $expand and also by directly following a path. Two examples are shown below. My $metaddata.xml file is attached, and also a single record from the Account table in which the relevant comparison seems to happen. the uuidUser property you can find here.
> I do not understand the error message. What is not clear to me is the assignment which is mentioned there g1.uuidUser = g0.fkProfile
> Just for your awareness, uuidUser and fkProfile are different columns of different types that should not be compared in anyway. Maybe this is a hint what is going wrong. I would the relevant NavigationProperty expect to be
> <NavigationProperty Name="fkProfileInProfile" Type="my_nutri_diary.Account" Nullable="false">
> <ReferentialConstraint Property="fkProfile" ReferencedProperty="idProfile"/>
> Here are two example queries which fail with the same error
> http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)?$expand=fkPro...
> http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)/fkProfileInPr...
> <error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
> <code>TEIID31172</code>
> <message>
> TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
> </message>
> </error>
> ----------------------------
> Update 9.1.19: I need to to add here, that there might be a second bug involved into the observation. It seems, that the error is due to type comparisons. As there was a comparison with Account.uuuiUser in the error message and as my table Account just holds a one to one mapping between uuids and integers which represent database internal IDs, I switched the primary key in the Account table from uuidUser to idProfile in hope to circumvent the bug.
> So my new observation is, when I disable row constraints in which I must have a comparison against uuidUser in the form "Profile.fkProfile in (SELECT Account.idProfile FROM Account WHERE Account.uuidUser = LEFT(user(), 36))" and switch hte primary key as mention previously, than I can follow the navigation property. However, as soon as I enable row constraints again I get a similar error message as before:
> <error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
> <code>TEIID31172</code>
> <message>
> TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
> </message>
> </error>
> As I am not sure if the issue derives from the same place in code, I thought I should add this here.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (TEIID-5589) NavigationProperty not working with Teiid odata, results in TEIID16053
by Christoph John (Jira)
[ https://issues.jboss.org/browse/TEIID-5589?page=com.atlassian.jira.plugin... ]
Christoph John updated TEIID-5589:
----------------------------------
Description:
Teiid throws an error in case it tries to follow an odata Navigation property. I tried this by using $expand and also by directly following a path. Two examples are shown below. My $metaddata.xml file is attached, and also a single record from the Account table in which the relevant comparison seems to happen. the uuidUser property you can find here.
I do not understand the error message. What is not clear to me is the assignment which is mentioned there g1.uuidUser = g0.fkProfile
Just for your awareness, uuidUser and fkProfile are different columns of different types that should not be compared in anyway. Maybe this is a hint what is going wrong. I would the relevant NavigationProperty expect to be
<NavigationProperty Name="fkProfileInProfile" Type="my_nutri_diary.Account" Nullable="false">
<ReferentialConstraint Property="fkProfile" ReferencedProperty="idProfile"/>
Here are two example queries which fail with the same error
http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)?$expand=fkPro...
http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)/fkProfileInPr...
<error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
<code>TEIID31172</code>
<message>
TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
</message>
</error>
----------------------------
Update 9.1.19: I need to to add here, that there might be a second bug involved into the observation. It seems, that the error is due to type comparisons. As there was a comparison with Account.uuuiUser in the error message and as my table Account just holds a one to one mapping between uuids and integers which represent database internal IDs, I switched the primary key in the Account table from uuidUser to idProfile in hope to circumvent the bug.
So my new observation is, when I disable row constraints in which I must have a comparison against uuidUser in the form "Profile.fkProfile in (SELECT Account.idProfile FROM Account WHERE Account.uuidUser = LEFT(user(), 36))" and switch hte primary key as mention previously, than I can follow the navigation property. However, as soon as I enable row constraints again I get a similar error message as before:
<error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
<code>TEIID31172</code>
<message>
TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
</message>
</error>
As I am not sure if the issue derives from the same place in code, I thought I should add this here.
was:
Teiid throws an error in case it tries to follow an odata Navigation property. I tried this by using $expand and also by directly following a path. Two examples are shown below. My $metaddata.xml file is attached, and also a single record from the Account table in which the relevant comparison seems to happen. the uuidUser property you can find here.
I do not understand the error message. What is not clear to me is the assignment which is mentioned there g1.uuidUser = g0.fkProfile
Just for your awareness, uuidUser and fkProfile are different columns of different types that should not be compared in anyway. Maybe this is a hint what is going wrong. I would the relevant NavigationProperty expect to be
<NavigationProperty Name="fkProfileInProfile" Type="my_nutri_diary.Account" Nullable="false">
<ReferentialConstraint Property="fkProfile" ReferencedProperty="idProfile"/>
Here are two example queries which fail with the same error
http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)?$expand=fkPro...
http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)/fkProfileInPr...
<error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
<code>TEIID31172</code>
<message>
TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
</message>
</error>
> NavigationProperty not working with Teiid odata, results in TEIID16053
> ------------------------------------------------------------------------
>
> Key: TEIID-5589
> URL: https://issues.jboss.org/browse/TEIID-5589
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 11.2.1
> Reporter: Christoph John
> Assignee: Steven Hawkins
> Priority: Blocker
> Attachments: AccountRecord.xml, metadata.xml
>
>
> Teiid throws an error in case it tries to follow an odata Navigation property. I tried this by using $expand and also by directly following a path. Two examples are shown below. My $metaddata.xml file is attached, and also a single record from the Account table in which the relevant comparison seems to happen. the uuidUser property you can find here.
> I do not understand the error message. What is not clear to me is the assignment which is mentioned there g1.uuidUser = g0.fkProfile
> Just for your awareness, uuidUser and fkProfile are different columns of different types that should not be compared in anyway. Maybe this is a hint what is going wrong. I would the relevant NavigationProperty expect to be
> <NavigationProperty Name="fkProfileInProfile" Type="my_nutri_diary.Account" Nullable="false">
> <ReferentialConstraint Property="fkProfile" ReferencedProperty="idProfile"/>
> Here are two example queries which fail with the same error
> http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)?$expand=fkPro...
> http://localhost:8080/odata4/vdb/my_nutri_diary/Profile(38)/fkProfileInPr...
> <error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
> <code>TEIID31172</code>
> <message>
> TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
> </message>
> </error>
> ----------------------------
> Update 9.1.19: I need to to add here, that there might be a second bug involved into the observation. It seems, that the error is due to type comparisons. As there was a comparison with Account.uuuiUser in the error message and as my table Account just holds a one to one mapping between uuids and integers which represent database internal IDs, I switched the primary key in the Account table from uuidUser to idProfile in hope to circumvent the bug.
> So my new observation is, when I disable row constraints in which I must have a comparison against uuidUser in the form "Profile.fkProfile in (SELECT Account.idProfile FROM Account WHERE Account.uuidUser = LEFT(user(), 36))" and switch hte primary key as mention previously, than I can follow the navigation property. However, as soon as I enable row constraints again I get a similar error message as before:
> <error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
> <code>TEIID31172</code>
> <message>
> TEIID31172 Could not resolve expressions being compared to a common type excluding character conversions: g1.uuidUser = g0.fkProfile
> </message>
> </error>
> As I am not sure if the issue derives from the same place in code, I thought I should add this here.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (TEIID-5590) vdb-maven-plugin - version 1.3 breaks build lifecycle
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIID-5590?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5590:
-------------------------------------
It was taken out explicitly not to process resources as the theses have no significance in .vdb packaged artifact. I wouldn't say it is breaking it, it is skipping. Have you considered other plug in s perhaps for this task?
> vdb-maven-plugin - version 1.3 breaks build lifecycle
> -----------------------------------------------------
>
> Key: TEIID-5590
> URL: https://issues.jboss.org/browse/TEIID-5590
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits, VDB
> Environment: {code}
> 2019-01-08 15:49:30
> rbellamy@eanna i ~/Development/Terradatum/metrics-vdb master % uname -a
> Linux eanna 4.20.0-arch1-1-ARCH #1 SMP PREEMPT Mon Dec 24 03:00:40 UTC 2018 x86_64 GNU/Linux
> 2019-01-08 15:52:36
> rbellamy@eanna i ~/Development/Terradatum/metrics-vdb master % mvn -v
> Apache Maven 3.5.4 (NON-CANONICAL_2018-09-08T01:02:16+02:00_root; 2018-09-07T16:02:16-07:00)
> Maven home: /opt/maven
> Java version: 1.8.0_192, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-8-openjdk/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.20.0-arch1-1-arch", arch: "amd64", family: "unix"
> 2019-01-08 15:52:40
> rbellamy@eanna i ~/Development/Terradatum/metrics-vdb master % java -version
> openjdk version "1.8.0_192"
> OpenJDK Runtime Environment (build 1.8.0_192-b26)
> OpenJDK 64-Bit Server VM (build 25.192-b26, mixed mode)
> {code}
> Reporter: G. Richard Bellamy
> Assignee: Barry LaFond
> Priority: Major
>
> When building a VDB with version 1.3 of the vdb-maven-plugin, the {{src/main/resources}} directory is NOT processed as expected. When using version 1.1, the "package" phase has the following (correct) phases:
> {code}
> [INFO] 'package' is a phase corresponding to this plugin:
> org.teiid:vdb-maven-plugin:vdb
> It is a part of the lifecycle for the POM packaging 'vdb'. This lifecycle includes the following phases:
> * validate: Not defined
> * initialize: Not defined
> * generate-sources: Not defined
> * process-sources: Not defined
> * generate-resources: Not defined
> * process-resources: org.apache.maven.plugins:maven-resources-plugin:resources
> * compile: org.apache.maven.plugins:maven-compiler-plugin:compile
> * process-classes: Not defined
> * generate-test-sources: Not defined
> * process-test-sources: Not defined
> * generate-test-resources: Not defined
> * process-test-resources: org.apache.maven.plugins:maven-resources-plugin:testResources
> * test-compile: org.apache.maven.plugins:maven-compiler-plugin:testCompile
> * process-test-classes: Not defined
> * test: org.apache.maven.plugins:maven-surefire-plugin:test
> * prepare-package: Not defined
> * package: org.teiid:vdb-maven-plugin:vdb
> * pre-integration-test: Not defined
> * integration-test: Not defined
> * post-integration-test: Not defined
> * verify: Not defined
> * install: org.apache.maven.plugins:maven-install-plugin:install
> * deploy: org.apache.maven.plugins:maven-deploy-plugin:deploy
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (TEIID-5590) vdb-maven-plugin - version 1.3 breaks build lifecycle
by G. Richard Bellamy (Jira)
G. Richard Bellamy created TEIID-5590:
-----------------------------------------
Summary: vdb-maven-plugin - version 1.3 breaks build lifecycle
Key: TEIID-5590
URL: https://issues.jboss.org/browse/TEIID-5590
Project: Teiid
Issue Type: Bug
Components: Build/Kits, VDB
Environment: {code}
2019-01-08 15:49:30
rbellamy@eanna i ~/Development/Terradatum/metrics-vdb master % uname -a
Linux eanna 4.20.0-arch1-1-ARCH #1 SMP PREEMPT Mon Dec 24 03:00:40 UTC 2018 x86_64 GNU/Linux
2019-01-08 15:52:36
rbellamy@eanna i ~/Development/Terradatum/metrics-vdb master % mvn -v
Apache Maven 3.5.4 (NON-CANONICAL_2018-09-08T01:02:16+02:00_root; 2018-09-07T16:02:16-07:00)
Maven home: /opt/maven
Java version: 1.8.0_192, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-8-openjdk/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.20.0-arch1-1-arch", arch: "amd64", family: "unix"
2019-01-08 15:52:40
rbellamy@eanna i ~/Development/Terradatum/metrics-vdb master % java -version
openjdk version "1.8.0_192"
OpenJDK Runtime Environment (build 1.8.0_192-b26)
OpenJDK 64-Bit Server VM (build 25.192-b26, mixed mode)
{code}
Reporter: G. Richard Bellamy
Assignee: Barry LaFond
When building a VDB with version 1.3 of the vdb-maven-plugin, the {{src/main/resources}} directory is NOT processed as expected. When using version 1.1, the "package" phase has the following (correct) phases:
{code}
[INFO] 'package' is a phase corresponding to this plugin:
org.teiid:vdb-maven-plugin:vdb
It is a part of the lifecycle for the POM packaging 'vdb'. This lifecycle includes the following phases:
* validate: Not defined
* initialize: Not defined
* generate-sources: Not defined
* process-sources: Not defined
* generate-resources: Not defined
* process-resources: org.apache.maven.plugins:maven-resources-plugin:resources
* compile: org.apache.maven.plugins:maven-compiler-plugin:compile
* process-classes: Not defined
* generate-test-sources: Not defined
* process-test-sources: Not defined
* generate-test-resources: Not defined
* process-test-resources: org.apache.maven.plugins:maven-resources-plugin:testResources
* test-compile: org.apache.maven.plugins:maven-compiler-plugin:testCompile
* process-test-classes: Not defined
* test: org.apache.maven.plugins:maven-surefire-plugin:test
* prepare-package: Not defined
* package: org.teiid:vdb-maven-plugin:vdb
* pre-integration-test: Not defined
* integration-test: Not defined
* post-integration-test: Not defined
* verify: Not defined
* install: org.apache.maven.plugins:maven-install-plugin:install
* deploy: org.apache.maven.plugins:maven-deploy-plugin:deploy
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months