[JBoss JIRA] (TEIID-2849) MongoDB: Provide basic metadata support
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2849?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2849.
---------------------------------
> MongoDB: Provide basic metadata support
> ---------------------------------------
>
> Key: TEIID-2849
> URL: https://issues.jboss.org/browse/TEIID-2849
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Affects Versions: 8.7
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: mongodb
> Fix For: 8.7
>
>
> Currently there is no native metadata import support in the MongoDB translator. It was avoided int he first run because there is no good way to interpret the complex document records. This position has not changed, but this enhancement request is to see if it can capture simple documents or top level documents as a starting point to capture and then to improve upon manually using tooling.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-2827) Can the teiid object associated with where the problem is found be added to the error message
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2827?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2827.
---------------------------------
> Can the teiid object associated with where the problem is found be added to the error message
> ---------------------------------------------------------------------------------------------
>
> Key: TEIID-2827
> URL: https://issues.jboss.org/browse/TEIID-2827
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.4.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 8.7
>
> Attachments: createdb.sql, perf-vdb-postgres.xml
>
>
> Using the attached dynamic vdb, against the database that was created using the attached DDL, produces the following errors:
> ERROR: Element Perf.HISTORY."TIME" of history is neither nullable nor has a default value. A value must be specified in the insert.
> ERROR: Element Perf.HISTORY.FILL of history is neither nullable nor has a default value. A value must be specified in the insert.
> Because of these errors, the VDB isn't deployed.
> Not sure why these are not just WARNINGS.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3076) Add materialized view to data-federation quick start
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3076?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3076.
---------------------------------
> Add materialized view to data-federation quick start
> ----------------------------------------------------
>
> Key: TEIID-3076
> URL: https://issues.jboss.org/browse/TEIID-3076
> Project: Teiid
> Issue Type: Enhancement
> Components: Quick Starts
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Minor
>
> Adding the following materialized view to the portfolio VDB to materialized the stocks view to TTL of 2 minutes:
> CREATE view stockPricesMatView
> (
> product_id integer,
> symbol string,
> price bigdecimal,
> company_name varchar(256)
> ) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'TRUE',
> MATERIALIZED_TABLE 'Accounts.h2_stock_mat',
> "teiid_rel:MATVIEW_TTL" 120000,
> "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'execute accounts.native(''truncate table h2_stock_mat'');',
> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute accounts.native('''')',
> "teiid_rel:ON_VDB_DROP_SCRIPT" 'DELETE FROM Accounts.status WHERE Name=''stock'' AND schemaname = ''Stocks''',
> "teiid_rel:MATERIALIZED_STAGE_TABLE" 'Accounts.h2_stock_mat',
> "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true',
> "teiid_rel:MATVIEW_STATUS_TABLE" 'status',
> "teiid_rel:MATVIEW_SHARE_SCOPE" 'NONE',
> "teiid_rel:MATVIEW_ONERROR_ACTION" 'THROW_EXCEPTION')
> AS SELECT A.ID, S.symbol, S.price, A.COMPANY_NAME
> FROM Stocks.StockPrices AS S, Accounts.PRODUCT AS A
> WHERE S.symbol = A.SYMBOL;
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3129) Limit is not added with multiple nulls in select on outer query to an inline view
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3129?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3129.
---------------------------------
> Limit is not added with multiple nulls in select on outer query to an inline view
> ---------------------------------------------------------------------------------
>
> Key: TEIID-3129
> URL: https://issues.jboss.org/browse/TEIID-3129
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.9
> Reporter: Sanjeev Gour
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> When a query does multiple null selects in the in the outer query to an inline view and you only have a DISTINCT constant selected from the view definition, a limit 1 is expected to be applied to the inline view query which does not happen. Here is the sample query-
> SELECT DISTINCT c1, null as c2, null as c3 FROM(
> SELECT c1, c2 FROM (
> SELECT 'const_col_1' as c1, ID as c2 FROM FIRST_SCHEMA.FIRST_TABLE
> UNION ALL
> SELECT 'const_col_2' as c1, ID as c2 FROM SECOND_SCHEMA.SECOND_TABLE
> ) as v
> ) as v1
> The query will contain queries to the inline view without a limit like the following-
> SELECT 'const_col_1' FROM h2extended.TEST.FIRST_SCHEMA.FIRST_TABLE AS g_0 -------------------LIMIT 1 is not applied here
> Full query plan and the detail are capture in this discussion-
> https://developer.jboss.org/thread/248787
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-2873) VDB re-deploy issue with VDB that auto-generates REST wars
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2873?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2873.
---------------------------------
> VDB re-deploy issue with VDB that auto-generates REST wars
> ----------------------------------------------------------
>
> Key: TEIID-2873
> URL: https://issues.jboss.org/browse/TEIID-2873
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.4
> Reporter: Mark Drilling
> Assignee: Ramesh Reddy
> Labels: Beta2
> Fix For: 8.7
>
> Attachments: ServerLog.txt
>
>
> I've encountered an issue when re-deploying a VDB that auto-generates and deploys REST wars. On re-deploy of the VDB, the REST wars don't always get deployed.
> Steps to reproduce and server.log is attached.
> Note this is on deploy of the VDB over an existing deployment. Workaround would be to explicitly un-deploy the VDB before doing the deploy.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-2809) Support for property substitution in vdb.xml files
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2809?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2809.
---------------------------------
> Support for property substitution in vdb.xml files
> --------------------------------------------------
>
> Key: TEIID-2809
> URL: https://issues.jboss.org/browse/TEIID-2809
> Project: Teiid
> Issue Type: Enhancement
> Affects Versions: 8.5
> Environment: EAP 6.1 Alpha , Teiid 8.5
> Reporter: Madhu Garimilla
> Assignee: Ramesh Reddy
> Labels: Alpha2
> Fix For: 8.7
>
>
> I have created a vdb.xml where i have declared my translators in it. I would like to pass some parameters to one of my translators so that i do not need to change my vdb.xml whenever there is a change in value. These parameters derive the values from the system properties. So, i am using ${} notation to pass the value of the system properties to my translator. When i try to deploy my VDB and try to access the parameters inside the translator, These system properties are not being resolved to the actual values.
> As per the thread https://community.jboss.org/thread/236325, this is not being supported as of now and requires an enhancement.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-2754) DatabaseMetaData reports views as tables
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2754?page=com.atlassian.jira.plugin... ]
Steven Hawkins reopened TEIID-2754:
-----------------------------------
Reopening to update docs.
> DatabaseMetaData reports views as tables
> ----------------------------------------
>
> Key: TEIID-2754
> URL: https://issues.jboss.org/browse/TEIID-2754
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver, Query Engine
> Affects Versions: 8.4
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.6, 9.0
>
>
> The client already has a check for isVirtual & system table type to report a "system view".
> We have a "View" type in our metadata, but we generally do not use it in our metadata code.
> So we either could set the view type on the server (although this seems like a broad change) or add another DatabaseMetaData check for isVirtual & table.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months