[JBoss JIRA] (TEIIDDES-3095) When view is selected to be materialized, can the user choose which extension properties to use
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3095?page=com.atlassian.jira.plu... ]
Van Halbert edited comment on TEIIDDES-3095 at 7/17/17 4:16 PM:
----------------------------------------------------------------
The materialize settings for the new view will be different. An example xml based materialization is below:
{code}
CREATE VIEW Stock (
product_id integer,
symbol string,
price double,
company_name string) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'TRUE',
MATERIALIZED_TABLE 'StockJDGSource.StockCache',
"teiid_rel:MATERIALIZED_STAGE_TABLE" 'StockJDGSource.ST_StockCache',
"teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'TRUE',
"teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'execute StockJDGSource.native(''truncate StockJDGSource.ST_StockCache'');',
"teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute StockJDGSource.native(''rename StockJDGSource.ST_StockCache StockJDGSource.StockCache'');',
"teiid_rel:MATVIEW_STATUS_TABLE" 'Accounts.status',
"teiid_rel:MATVIEW_TTL" 10000,
"teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT')
AS
SELECT
Stocks.Stock.product_id, Stocks.Stock.symbol, CAST(Stocks.Stock.price AS double) AS price, Stocks.Stock.company_name
FROM
Stocks.Stock;
{code}
Note the BEFORE and AFTER procedures are different
was (Author: van.halbert):
The materialize settings for the new view will be different. An example xml based materialization is below:
{code}
CREATE VIEW Stock (
product_id integer,
symbol string,
price double,
company_name string) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'TRUE',
MATERIALIZED_TABLE 'StockJDGSource.StockCache',
"teiid_rel:MATERIALIZED_STAGE_TABLE" 'StockJDGSource.ST_StockCache',
"teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'TRUE',
"teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'execute StockJDGSource.native(''truncate StockJDGSource.ST_StockCache'');',
"teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute StockJDGSource.native(''rename StockJDGSource.ST_StockCache StockJDGSource.StockCache'');',
"teiid_rel:MATVIEW_STATUS_TABLE" 'Accounts.status',
"teiid_rel:MATVIEW_TTL" 10000,
"teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT')
AS
SELECT
Stocks.Stock.product_id, Stocks.Stock.symbol, CAST(Stocks.Stock.price AS double) AS price, Stocks.Stock.company_name
FROM
Stocks.Stock;
{code}
> When view is selected to be materialized, can the user choose which extension properties to use
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-3095
> URL: https://issues.jboss.org/browse/TEIIDDES-3095
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling
> Affects Versions: 11.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 11.0.2
>
>
> With the support of the new infinispan-hotrod (JDG 7.1) translator that will be used, there is a different extension properties to be used. And when the user selects a view to be materialized, can an option be added to the first panel (which shows the source and target models) that allows the user to select which extension properties to use? And if they choose the option for JDG 7.1, then no need to goto next panel (create pojo).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 9 months
[JBoss JIRA] (TEIIDDES-3095) When view is selected to be materialized, can the user choose which extension properties to use
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3095?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-3095:
---------------------------------------
The materialize settings for the new view will be different. An example xml based materialization is below:
{code}
CREATE VIEW Stock (
product_id integer,
symbol string,
price double,
company_name string) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'TRUE',
MATERIALIZED_TABLE 'StockJDGSource.StockCache',
"teiid_rel:MATERIALIZED_STAGE_TABLE" 'StockJDGSource.ST_StockCache',
"teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'TRUE',
"teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'execute StockJDGSource.native(''truncate StockJDGSource.ST_StockCache'');',
"teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute StockJDGSource.native(''rename StockJDGSource.ST_StockCache StockJDGSource.StockCache'');',
"teiid_rel:MATVIEW_STATUS_TABLE" 'Accounts.status',
"teiid_rel:MATVIEW_TTL" 10000,
"teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT')
AS
SELECT
Stocks.Stock.product_id, Stocks.Stock.symbol, CAST(Stocks.Stock.price AS double) AS price, Stocks.Stock.company_name
FROM
Stocks.Stock;
{code}
> When view is selected to be materialized, can the user choose which extension properties to use
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-3095
> URL: https://issues.jboss.org/browse/TEIIDDES-3095
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling
> Affects Versions: 11.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 11.0.2
>
>
> With the support of the new infinispan-hotrod (JDG 7.1) translator that will be used, there is a different extension properties to be used. And when the user selects a view to be materialized, can an option be added to the first panel (which shows the source and target models) that allows the user to select which extension properties to use? And if they choose the option for JDG 7.1, then no need to goto next panel (create pojo).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 9 months
[JBoss JIRA] (TEIIDDES-3090) Parsing error on Preview in Teiid Designer if the source column has a default value
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3090?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-3090:
----------------------------------------
[~dsteigne] This is due to the nature/limitations of "default value" strings. In this case
*'user name'::text* is the culprit (.. note if you defined the entire string as *'\'user name\'::text'* it would work)
In TEIIDDES-2888 the default value *('STOCK')*
In both cases, the Teiid parser expecting a single string enclosed in single quotes and everything in-between needs to be properly escaped.
Since in your case and TEIIDDES-2888, the default value string is being imported and I'm not sure if we should auto-correct/alter users's metadata.
> Parsing error on Preview in Teiid Designer if the source column has a default value
> -----------------------------------------------------------------------------------
>
> Key: TEIIDDES-3090
> URL: https://issues.jboss.org/browse/TEIIDDES-3090
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview
> Affects Versions: 11.0.1
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
>
> Parsing error[1] on Preview in Teiid Designer if the source column has a default value.
> [1]
> 13:40:03,990 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB PREVIEW-32405570-21e1-4a40-ace7-21b408420884.1 model "debschema" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered ") DEFAULT ''[*]user[*] name'::text'" at line 4, column 47.
> Was expecting: "options" | "," | ")": org.teiid.metadata.ParseException: TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered ") DEFAULT ''[*]user[*] name'::text'" at line 4, column 47.
> Was expecting: "options" | "," | ")"
> at org.teiid.query.parser.QueryParser.parseDDL(QueryParser.java:472) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.metadata.MetadataFactory.parse(MetadataFactory.java:769) [teiid-api-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.query.metadata.DDLMetadataRepository.loadMetadata(DDLMetadataRepository.java:40) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.runtime.AbstractVDBDeployer$MetadataRepositoryWrapper.loadMetadata(AbstractVDBDeployer.java:84) [teiid-runtime-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.jboss.VDBService$7.run(VDBService.java:446) [teiid-jboss-integration-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_60]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_60]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered ") DEFAULT ''[*]user[*] name'::text'" at line 4, column 47.
> Was expecting: "options" | "," | ")"
> at org.teiid.query.parser.QueryParser.convertParserException(QueryParser.java:214) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> ... 11 more
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 9 months
[JBoss JIRA] (TEIIDDES-3095) When view is selected to be materialized, can the user choose which extension properties to use
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3095?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-3095:
---------------------------------------
In the current designer, you select "Materialize", it walks you thru a wizard:
1. (1st panel) Enter the name of the new Source Model to put the new matview and staging source tables.
2 (2nd panel) select option to generate pojo
results: create 2 source tables, where the staging table has an extension property (Primary table) to indicates which source table is the matview source.
To support JDG 7.1, there is a different set of extension properties that apply (the JDG 6.x properties are not used), example: "infinispan-hotrod":"CACHE", is the important one.
What do we need changed:
- on the 1st panel, enable the user to select which JDG they are using: JDG 7.1 or JDG 6.6
- based on selection do the following:
JDG 6.6 - set namespace to "infinispan"
JDG 7.1 - set namespace to "infinispan-hotrod"
if JDG 6.6 is selected, enable "NEXT" and "FINISH" - do as it does now
if JDG 7.1 is selected, enable only "FINISH" (don't need to create pojo).
The wizard curently creates both tables (matview and staging), and that should remain the same.
> When view is selected to be materialized, can the user choose which extension properties to use
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-3095
> URL: https://issues.jboss.org/browse/TEIIDDES-3095
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling
> Affects Versions: 11.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 11.0.2
>
>
> With the support of the new infinispan-hotrod (JDG 7.1) translator that will be used, there is a different extension properties to be used. And when the user selects a view to be materialized, can an option be added to the first panel (which shows the source and target models) that allows the user to select which extension properties to use? And if they choose the option for JDG 7.1, then no need to goto next panel (create pojo).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 9 months
[JBoss JIRA] (TEIIDDES-3095) When view is selected to be materialized, can the user choose which extension properties to use
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3095?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-3095:
-----------------------------------
Fix Version/s: 11.0.2
> When view is selected to be materialized, can the user choose which extension properties to use
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-3095
> URL: https://issues.jboss.org/browse/TEIIDDES-3095
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling
> Affects Versions: 11.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 11.0.2
>
>
> With the support of the new infinispan-hotrod (JDG 7.1) translator that will be used, there is a different extension properties to be used. And when the user selects a view to be materialized, can an option be added to the first panel (which shows the source and target models) that allows the user to select which extension properties to use? And if they choose the option for JDG 7.1, then no need to goto next panel (create pojo).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 9 months
[JBoss JIRA] (TEIIDDES-3095) When view is selected to be materialized, can the user choose which extension properties to use
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3095?page=com.atlassian.jira.plu... ]
Van Halbert updated TEIIDDES-3095:
----------------------------------
Description: With the support of the new infinispan-hotrod (JDG 7.1) translator that will be used, there is a different extension properties to be used. And when the user selects a view to be materialized, can an option be added to the first panel (which shows the source and target models) that allows the user to select which extension properties to use? And if they choose the option for JDG 7.1, then no need to goto next panel (create pojo). (was: With the support of the new infinispan-hotrod (JDG 7.1) translator that will be used, there is a different extension properties to be used. And when the user selects a view to be materialized, can an option be added to the first panel (which shows the source and target models) that allows the user to select which option to use? And if they choose the option for JDG 7.1, then no need to goto next panel (create pojo).)
> When view is selected to be materialized, can the user choose which extension properties to use
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-3095
> URL: https://issues.jboss.org/browse/TEIIDDES-3095
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling
> Affects Versions: 11.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
>
> With the support of the new infinispan-hotrod (JDG 7.1) translator that will be used, there is a different extension properties to be used. And when the user selects a view to be materialized, can an option be added to the first panel (which shows the source and target models) that allows the user to select which extension properties to use? And if they choose the option for JDG 7.1, then no need to goto next panel (create pojo).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 9 months
[JBoss JIRA] (TEIIDDES-3095) When view is selected to be materialized, can the user choose which extension properties to use
by Van Halbert (JIRA)
Van Halbert created TEIIDDES-3095:
-------------------------------------
Summary: When view is selected to be materialized, can the user choose which extension properties to use
Key: TEIIDDES-3095
URL: https://issues.jboss.org/browse/TEIIDDES-3095
Project: Teiid Designer
Issue Type: Enhancement
Components: Modeling
Affects Versions: 11.1
Reporter: Van Halbert
With the support of the new infinispan-hotrod (JDG 7.1) translator that will be used, there is a different extension properties to be used. And when the user selects a view to be materialized, can an option be added to the first panel (which shows the source and target models) that allows the user to select which option to use? And if they choose the option for JDG 7.1, then no need to goto next panel (create pojo).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 9 months
[JBoss JIRA] (TEIIDDES-3095) When view is selected to be materialized, can the user choose which extension properties to use
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3095?page=com.atlassian.jira.plu... ]
Van Halbert reassigned TEIIDDES-3095:
-------------------------------------
Assignee: Barry LaFond
> When view is selected to be materialized, can the user choose which extension properties to use
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-3095
> URL: https://issues.jboss.org/browse/TEIIDDES-3095
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling
> Affects Versions: 11.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
>
> With the support of the new infinispan-hotrod (JDG 7.1) translator that will be used, there is a different extension properties to be used. And when the user selects a view to be materialized, can an option be added to the first panel (which shows the source and target models) that allows the user to select which option to use? And if they choose the option for JDG 7.1, then no need to goto next panel (create pojo).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 9 months
[JBoss JIRA] (TEIIDDES-3071) SQL transformation editor rewrites TRIM() function incorrectly most of the time
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3071?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-3071.
------------------------------------
Resolution: Done
11.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/49f77745215cdc29e... https://github.com/Teiid-Designer/teiid-designer/commit/93483586ed3713b8e...
> SQL transformation editor rewrites TRIM() function incorrectly most of the time
> -------------------------------------------------------------------------------
>
> Key: TEIIDDES-3071
> URL: https://issues.jboss.org/browse/TEIIDDES-3071
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations
> Affects Versions: 11.0.1
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 11.0.2
>
>
> Paste the below SQL in the transformation editor to create a view table:
> SELECT
> trim(INTKEY),trim(STRINGKEY),trim(INTNUM),trim(STRINGNUM),trim(FLOATNUM),trim(LONGNUM),trim(DOUBLENUM),trim(BYTENUM),trim(DATEVALUE),trim(TIMESTAMPVALUE), trim(BOOLEANVALUE),trim(CHARVALUE),trim(SHORTVALUE),trim(BIGINTEGERVALUE),trim(BIGDECIMALVALUE),trim(OBJECTVALUE)
> FROM
> bqtora.LARGEB
> Once you save it, it gets rewritten with the defaults, but it leaves the column name out most of the time:
> SELECT
> trim(' ' FROM ), trim(' ' FROM bqtora.LARGEB.STRINGKEY), trim(' ' FROM ), trim(' ' FROM bqtora.LARGEB.STRINGNUM), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM bqtora.LARGEB.OBJECTVALUE)
> FROM
> bqtora.LARGEB
> So obviously you receive a validation parsing error:
> ERROR: Error in parsing of sql - Encountered " ")" ") "" at line 2, column 31.
> Was expecting one of:
> "char" ...
> "date" ...
> "time" ...
> "timestamp" ...
> "cast" ...
> "convert" ...
> "any" ...
> "array_agg" ...
> "case" ...
> "exists" ...
> "false" ...
> "hour" ...
> "insert" ...
> "left" ...
> "minute" ...
> "month" ...
> "not" ...
> "null" ...
> "right" ...
> "second" ...
> "some" ...
> "translate" ...
> "true" ...
> "unknown" ...
> "user" ...
> "year" ...
> "xmlagg" ...
> "xmlcast" ...
> "xmlconcat" ...
> "xmlcomment" ...
> "xmlelement" ...
> "xmlexists" ...
> "xmlforest" ...
> "xmlparse" ...
> "xmlpi" ...
> "xmlquery" ...
> "xmlserialize" ...
> "xmltext" ...
> "instead" ...
> "enabled" ...
> "disabled" ...
> "view" ...
> "key" ...
> "serial" ...
> "textagg" ...
> "count" ...
> "row_number" ...
> "rank" ...
> "dense_rank" ...
> "sum" ...
> "avg" ...
> "min" ...
> "max" ...
> "every" ...
> "stddev_pop" ...
> "stddev_samp" ...
> "var_samp" ...
> "var_pop" ...
> "document" ...
> "content" ...
> "trim" ...
> "empty" ...
> "ordinality" ...
> "path" ...
> "first" ...
> "last" ...
> "next" ...
> "substring" ...
> "extract" ...
> "to_chars" ...
> "to_bytes" ...
> "timestampadd" ...
> "timestampdiff" ...
> "querystring" ...
> "namespace" ...
> "result" ...
> "index" ...
> "accesspattern" ...
> "auto_increment" ...
> "wellformed" ...
> "sql_tsi_frac_second" ...
> "sql_tsi_second" ...
> "sql_tsi_minute" ...
> "sql_tsi_hour" ...
> "sql_tsi_day" ...
> "sql_tsi_week" ...
> "sql_tsi_month" ...
> "sql_tsi_quarter" ...
> "sql_tsi_year" ...
> "texttable" ...
> "arraytable" ...
> "selector" ...
> "skip" ...
> "width" ...
> "passing" ...
> "name" ...
> "encoding" ...
> "columns" ...
> "delimiter" ...
> "quote" ...
> "header" ...
> "nulls" ...
> "objecttable" ...
> "version" ...
> "including" ...
> "excluding" ...
> "xmldeclaration" ...
> "variadic" ...
> "exception" ...
> "raise" ...
> "chain" ...
> "jsonarray_agg" ...
> "jsonobject" ...
> "preserve" ...
> <ID> ...
> <ESCAPEDFUNCTION> ...
> <ESCAPEDTYPE> ...
> <DECIMALVAL> ...
> <FLOATVAL> ...
> <STRINGVAL> ...
> <UNSIGNEDINTEGER> ...
> <BINARYSTRINGVAL> ...
> "(" ...
> "+" ...
> "-" ...
> "?" ...
> "$" ...
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 9 months