[
https://issues.jboss.org/browse/TEIID-5848?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5848:
---------------------------------------
What is "main datasource"? Datasource for vertica or
datasource for teiid embed metafata db? Can you give example?
In the context of your spring application if you use
{code}
@Autowire
DataSource dataSource;
{code}
Then that should provide the embedded data source for Teiid.
Another question. What is "primary key for view"?
It's something that can optionally be defined by the source. If the database does not
provide that metadata, then the view will not visible in Teiid OData - which requires the
notion of key to expose an entity.
In view we do not have any keys, what about view with multiple back
tables and sub tables?
The metadata import only does not try to obtain the view definition and transitively
determine if there are unique / primary keys.
In view we do not have any keys, what about view with multiple back tables and sub
tables?
views in vertica not found by teiid
-----------------------------------
Key: TEIID-5848
URL:
https://issues.jboss.org/browse/TEIID-5848
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Reporter: Renat Eskenin
Assignee: Steven Hawkins
Priority: Major
We created view in vertica DB
Example project with vertica translator+odata not found this view
{code}
src 1 Varchar 4 [NULL] true false false [NULL] false [NULL]
src_id 2 Varchar 18 [NULL] true false false [NULL] false [NULL]
src_name 3 Varchar 363 [NULL] true false false [NULL] false [NULL]
account_id 4 Varchar 18 [NULL] true false false [NULL] false [NULL]
name 5 Varchar 765 [NULL] true false false [NULL] false [NULL]
billing_country 6 Varchar 240 [NULL] true false false [NULL] false [NULL]
root_domain 7 Varchar 192 [NULL] true false false [NULL] false [NULL]
sales_team 8 Varchar 240 [NULL] true false false [NULL] false [NULL]
{code}
{
"error": {
"code": null,
"message": "Cannot find EntitySet, Singleton, ActionImport or
FunctionImport with name 'funnel_leads'."
}
}
But regular tables works properly
--
This message was sent by Atlassian Jira
(v7.13.8#713008)