[JBoss JIRA] (TEIID-2368) Dynamic VDB deployment fails when using importer.importIndexes in the case of a index containing a hidden column
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2368?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2368.
---------------------------------
> Dynamic VDB deployment fails when using importer.importIndexes in the case of a index containing a hidden column
> ----------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-2368
> URL: https://issues.jboss.org/browse/TEIID-2368
> Project: Teiid
> Issue Type: Feature Request
> Affects Versions: 8.2
> Reporter: Jack Ma
> Assignee: Steven Hawkins
> Fix For: 8.3
>
>
> We are trying to use dynamic VDB. For better performance, we use <property name="importer.importIndexes" value="true"/> to input the index for an oracle datasource.
>
> But vdb deployment failed with following error:
> [TEIID60011 No column found with name SYS_NC00032$]
>
> Debugging through teiid code, it looks like that if the index contains the hidden column (like SYS_NC00032), then index loading failed, teiid was trying to call getColumnByName() for those hidden column which does not exist in the column map.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (TEIID-2519) Odata Table Query Not Workng
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2519?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2519.
---------------------------------
> Odata Table Query Not Workng
> ----------------------------
>
> Key: TEIID-2519
> URL: https://issues.jboss.org/browse/TEIID-2519
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.3
> Environment: CentOS, JBOSS AS 7.1.1, Teiid 8.3.
> Reporter: devin pinkston
> Assignee: Ramesh Reddy
> Priority: Minor
> Labels: odata,, service,, web
> Fix For: 8.4
>
> Attachments: metadata.txt, portfolio-vdb.xml, portfolio-vdb.xml
>
>
> When trying to query a table through Odata, a error is diplayed: EdmEntitySet refinedSalariesModel.refinedSalaries is not found
> When issuing the query:
> http://localhost:8080/odata/Portfolio.1/refinedSalariesModel.refinedSalaries
> We have also tried using:
> http://localhost:8080/odata/Portfolio.1/refinedSalariesModel/refinedSalaries
> When issuing the second query, this error is thrown:
> <error><code/><message lang="en-US">Could not find resource for relative : /refinedSalariesModel/refinedSalaries of full path: http://localhost:8080/odata/Portfolio.1/refinedSalariesModel/refinedSalaries</message></error>
> We can successfully display the metadata and see the details of the VDB by using:
> http://localhost:8080/odata/Portfolio.1/$metadata
> Please let me know if you need any more information
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months