[JBoss JIRA] (TEIIDDES-2259) Edit VDB Data Role dialogue doesn't check off checkboxes properly
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2259?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2259:
-----------------------------------
Fix Version/s: 9.2
(was: 9.1)
> Edit VDB Data Role dialogue doesn't check off checkboxes properly
> -----------------------------------------------------------------
>
> Key: TEIIDDES-2259
> URL: https://issues.jboss.org/browse/TEIIDDES-2259
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3.3
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Fix For: 8.6.2, 9.2, 9.0.3
>
> Attachments: ReuseVDB_Dataroles.zip, screen1.png, Step2.png, Step3.png, Step4.png
>
>
> When I tick, for example, "Create" on one column and "Read" on the same column and then check off "Create", the gray checkboxes stay the same. Only after I check off "Read" on this column all disappear... screenshot attached
> JBDS 7.1.1.GA + Teiid Designer 8.3.3
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (TEIIDDES-2500) Problems with model created via import from Salesforce when using JOIN query
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2500?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2500:
-----------------------------------
Fix Version/s: 9.0.3
(was: 9.0.2)
> Problems with model created via import from Salesforce when using JOIN query
> ----------------------------------------------------------------------------
>
> Key: TEIIDDES-2500
> URL: https://issues.jboss.org/browse/TEIIDDES-2500
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.1
> Reporter: Matus Makovy
> Assignee: Mark Drilling
> Fix For: 9.1, 8.6.2, 9.0.3
>
> Attachments: log, salesdynamic-vdb.xml, SalesforceTD.zip
>
>
> Discovered this issue when trying to verify TEIID-3112
> I am trying to execute this query on VDB created via import from SalesForce in Teiid Designer.
> {quote}
> select distinct YEAR("Opportunity"."CloseDate") as "Opportunity_CloseDate1" from "SalesForceSource".salesforce.Campaign AS "Campaign" LEFT OUTER JOIN "SalesForceSource".salesforce.Opportunity AS "Opportunity" ON Campaign."Id" = Opportunity."CampaignId" order by YEAR("Opportunity"."CloseDate") ASC LIMIT 0 , 32
> {quote}
> And I get this exception:
> {quote}
> org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidException: Invalid QName in mapping: sf:INVALID_TYPE
> {quote}
> Log attached
> With dynamic VDB created manually or with import using Teiid Connection Importer via Designer everything works.
> Project from Designer + dynamic VDB attached
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (TEIIDDES-2052) 'Mark as Deployable' on a war not working for remote (OpenShift) server
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2052?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2052:
-----------------------------------
Fix Version/s: 9.2
(was: 9.1)
> 'Mark as Deployable' on a war not working for remote (OpenShift) server
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-2052
> URL: https://issues.jboss.org/browse/TEIIDDES-2052
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3.1
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 9.2
>
>
> I created a war (using Rest War generator) in Designer and added it to my project. Then to deploy it, I selected it and used the 'Mark as Deployable" action.
> This worked fine on my local server (both deploy and undeploy) but then I switched to an OpenShift external server instance (used port-forwarding).
> The 'Mark as Deployable' action doesnt work for the Openshift external server. Maybe the action is doing a copy of the war into the deployments folder?
> We don't provide the action, but we should either troubleshoot or potentially provide our own action which deploys a war using the admin api.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (TEIIDDES-2398) Inconsistent column datatypes when importing
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2398?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2398:
-----------------------------------
Fix Version/s: (was: 9.0.2)
> Inconsistent column datatypes when importing
> --------------------------------------------
>
> Key: TEIIDDES-2398
> URL: https://issues.jboss.org/browse/TEIIDDES-2398
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Modeling
> Reporter: Andrej Šmigala
> Assignee: Mark Drilling
> Fix For: 9.1, 8.6.2, 9.0.3
>
> Attachments: datatypes.png, MySQL_BQT_DDL.ddl
>
>
> There are multiple discrepancies in the column datatypes when importing using JDBC importer vs when using Teiid Connection importer.
> Also some of the imported datatypes seem completely wrong (e.g. bigdecimal for almost all numeric datatypes in oracle)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (TEIIDDES-2460) JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2460:
-----------------------------------
Fix Version/s: 9.0.3
(was: 9.0.2)
> JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2460
> URL: https://issues.jboss.org/browse/TEIIDDES-2460
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Barry LaFond
> Assignee: Mark Drilling
> Fix For: 9.1, 9.0.3
>
> Attachments: ErrorDialog.png
>
>
> When the JDBC importer is used to import a schema from an existing VDB integer types will be converted into biginterger types. This error is similar to Bug 1026892 except no exception is raised
> Version-Release number of selected component (if applicable):
> Actual results:
> Imported schema has changed integer data type to biginteger data type.
> Expected results:
> Imported schema will be identical to original schema.
> Additional info:
> Imported schema is so long as the JPA entity reflects the biginteger type. This is problematic because now two separate JPA entities are needed, one for the original schema and another for the imported schema.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (TEIIDDES-2398) Inconsistent column datatypes when importing
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2398?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2398:
-----------------------------------
Fix Version/s: 9.0.3
> Inconsistent column datatypes when importing
> --------------------------------------------
>
> Key: TEIIDDES-2398
> URL: https://issues.jboss.org/browse/TEIIDDES-2398
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Modeling
> Reporter: Andrej Šmigala
> Assignee: Mark Drilling
> Fix For: 9.1, 8.6.2, 9.0.3
>
> Attachments: datatypes.png, MySQL_BQT_DDL.ddl
>
>
> There are multiple discrepancies in the column datatypes when importing using JDBC importer vs when using Teiid Connection importer.
> Also some of the imported datatypes seem completely wrong (e.g. bigdecimal for almost all numeric datatypes in oracle)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (TEIIDDES-2259) Edit VDB Data Role dialogue doesn't check off checkboxes properly
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2259?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2259:
-----------------------------------
Fix Version/s: 9.0.3
(was: 9.0.2)
> Edit VDB Data Role dialogue doesn't check off checkboxes properly
> -----------------------------------------------------------------
>
> Key: TEIIDDES-2259
> URL: https://issues.jboss.org/browse/TEIIDDES-2259
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3.3
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Fix For: 9.1, 8.6.2, 9.0.3
>
> Attachments: ReuseVDB_Dataroles.zip, screen1.png, Step2.png, Step3.png, Step4.png
>
>
> When I tick, for example, "Create" on one column and "Read" on the same column and then check off "Create", the gray checkboxes stay the same. Only after I check off "Read" on this column all disappear... screenshot attached
> JBDS 7.1.1.GA + Teiid Designer 8.3.3
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (TEIIDDES-2502) Incorrect transformation reconciliation
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2502?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-2502:
---------------------------------------
Even when 1 table (i.e., ACCT.\*) is used, it still doesn't resolve correctly to replace all columns.
> Incorrect transformation reconciliation
> ---------------------------------------
>
> Key: TEIIDDES-2502
> URL: https://issues.jboss.org/browse/TEIIDDES-2502
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling, Transformations
> Affects Versions: 9.0.1
> Environment: 9.0.1.Final-v20150211-1407-B643
> JBDS / Designer on Windows
> Reporter: Tom Johnston
> Assignee: Barry LaFond
>
> SELECT
> proj.\*, act.\*, cm.Field_Num, cm.Identity_Token, f.Plant_Num
> FROM
> ((Table1 AS act LEFT OUTER JOIN Table2 AS proj ON proj.Field_ID = act.Field_ID) LEFT OUTER JOIN Table3 AS f ON f.Field_ID = act.Field_ID) INNER JOIN Table4 AS cm ON cm.Contract_ID = f.Contract_ID
> ORDER BY act.Crop_Year
> "resolves"
> to:
> SELECT
> Table2 AS proj.\*,
> Table1 AS act.\*, cm.Field_Num, cm.Identity_Token,
> f.Plant_Num
> FROM
> ((Table1 AS act LEFT OUTER JOIN
> Table2 AS proj ON proj.Field_ID = act.Field_ID)
> LEFT OUTER JOIN Table3 AS f ON f.Field_ID = act.Field_ID) INNER JOIN
> Table4 AS cm ON cm.Contract_ID = f.Contract_ID
> ORDER BY act.Crop_Year
> with error:
> ERROR: Error in parsing of sql - Encountered " <ALL_IN_GROUP> "proj.\* "" at
> line 2, column 54.
> Was expecting one of:
> "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" ...
> <ID> ...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (TEIIDDES-2502) Incorrect transformation reconciliation
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2502?page=com.atlassian.jira.plu... ]
Van Halbert edited comment on TEIIDDES-2502 at 5/15/15 7:23 AM:
----------------------------------------------------------------
It can be duplicated with any 2 tables.
Example with portfolio tables:
SELECT
ACCT.\*, PROD.\*
FROM
Accounts.ACCOUNT AS ACCT LEFT OUTER JOIN Accounts.PRODUCT AS PROD ON ACCT.ACCOUNT_ID = PROD.ID
Resolves to:
SELECT
Accounts.ACCOUNT AS ACCT.*, Accounts.PRODUCT AS PROD.*
FROM
Accounts.ACCOUNT AS ACCT LEFT OUTER JOIN Accounts.PRODUCT AS PROD ON ACCT.ACCOUNT_ID = PROD.ID
with error:
ERROR: Error in parsing of sql - Encountered " <ALL_IN_GROUP> "ACCT.* "" at line 2, column 37.
Was expecting one of:
"instead" ...
"enabled" ...
"disabled" ...
....
was (Author: van.halbert):
It can be duplicated with any 2 tables.
Example with portfolio tables:
SELECT
ACCT.\*, PROD.\*
FROM
Accounts.ACCOUNT AS ACCT LEFT OUTER JOIN Accounts.PRODUCT AS PROD ON ACCT.ACCOUNT_ID = PROD.ID
Resolves t:
SELECT
Accounts.ACCOUNT AS ACCT.*, Accounts.PRODUCT AS PROD.*
FROM
Accounts.ACCOUNT AS ACCT LEFT OUTER JOIN Accounts.PRODUCT AS PROD ON ACCT.ACCOUNT_ID = PROD.ID
with error:
ERROR: Error in parsing of sql - Encountered " <ALL_IN_GROUP> "ACCT.* "" at line 2, column 37.
Was expecting one of:
"instead" ...
"enabled" ...
"disabled" ...
....
> Incorrect transformation reconciliation
> ---------------------------------------
>
> Key: TEIIDDES-2502
> URL: https://issues.jboss.org/browse/TEIIDDES-2502
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling, Transformations
> Affects Versions: 9.0.1
> Environment: 9.0.1.Final-v20150211-1407-B643
> JBDS / Designer on Windows
> Reporter: Tom Johnston
> Assignee: Barry LaFond
>
> SELECT
> proj.\*, act.\*, cm.Field_Num, cm.Identity_Token, f.Plant_Num
> FROM
> ((Table1 AS act LEFT OUTER JOIN Table2 AS proj ON proj.Field_ID = act.Field_ID) LEFT OUTER JOIN Table3 AS f ON f.Field_ID = act.Field_ID) INNER JOIN Table4 AS cm ON cm.Contract_ID = f.Contract_ID
> ORDER BY act.Crop_Year
> "resolves"
> to:
> SELECT
> Table2 AS proj.\*,
> Table1 AS act.\*, cm.Field_Num, cm.Identity_Token,
> f.Plant_Num
> FROM
> ((Table1 AS act LEFT OUTER JOIN
> Table2 AS proj ON proj.Field_ID = act.Field_ID)
> LEFT OUTER JOIN Table3 AS f ON f.Field_ID = act.Field_ID) INNER JOIN
> Table4 AS cm ON cm.Contract_ID = f.Contract_ID
> ORDER BY act.Crop_Year
> with error:
> ERROR: Error in parsing of sql - Encountered " <ALL_IN_GROUP> "proj.\* "" at
> line 2, column 54.
> Was expecting one of:
> "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" ...
> <ID> ...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (TEIIDDES-2502) Incorrect transformation reconciliation
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2502?page=com.atlassian.jira.plu... ]
Van Halbert edited comment on TEIIDDES-2502 at 5/15/15 7:23 AM:
----------------------------------------------------------------
It can be duplicated with any 2 tables.
Example with portfolio tables:
SELECT
ACCT.\*, PROD.\*
FROM
Accounts.ACCOUNT AS ACCT LEFT OUTER JOIN Accounts.PRODUCT AS PROD ON ACCT.ACCOUNT_ID = PROD.ID
Resolves to:
SELECT
Accounts.ACCOUNT AS ACCT.\*, Accounts.PRODUCT AS PROD.\*
FROM
Accounts.ACCOUNT AS ACCT LEFT OUTER JOIN Accounts.PRODUCT AS PROD ON ACCT.ACCOUNT_ID = PROD.ID
with error:
ERROR: Error in parsing of sql - Encountered " <ALL_IN_GROUP> "ACCT.* "" at line 2, column 37.
Was expecting one of:
"instead" ...
"enabled" ...
"disabled" ...
....
was (Author: van.halbert):
It can be duplicated with any 2 tables.
Example with portfolio tables:
SELECT
ACCT.\*, PROD.\*
FROM
Accounts.ACCOUNT AS ACCT LEFT OUTER JOIN Accounts.PRODUCT AS PROD ON ACCT.ACCOUNT_ID = PROD.ID
Resolves to:
SELECT
Accounts.ACCOUNT AS ACCT.*, Accounts.PRODUCT AS PROD.*
FROM
Accounts.ACCOUNT AS ACCT LEFT OUTER JOIN Accounts.PRODUCT AS PROD ON ACCT.ACCOUNT_ID = PROD.ID
with error:
ERROR: Error in parsing of sql - Encountered " <ALL_IN_GROUP> "ACCT.* "" at line 2, column 37.
Was expecting one of:
"instead" ...
"enabled" ...
"disabled" ...
....
> Incorrect transformation reconciliation
> ---------------------------------------
>
> Key: TEIIDDES-2502
> URL: https://issues.jboss.org/browse/TEIIDDES-2502
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling, Transformations
> Affects Versions: 9.0.1
> Environment: 9.0.1.Final-v20150211-1407-B643
> JBDS / Designer on Windows
> Reporter: Tom Johnston
> Assignee: Barry LaFond
>
> SELECT
> proj.\*, act.\*, cm.Field_Num, cm.Identity_Token, f.Plant_Num
> FROM
> ((Table1 AS act LEFT OUTER JOIN Table2 AS proj ON proj.Field_ID = act.Field_ID) LEFT OUTER JOIN Table3 AS f ON f.Field_ID = act.Field_ID) INNER JOIN Table4 AS cm ON cm.Contract_ID = f.Contract_ID
> ORDER BY act.Crop_Year
> "resolves"
> to:
> SELECT
> Table2 AS proj.\*,
> Table1 AS act.\*, cm.Field_Num, cm.Identity_Token,
> f.Plant_Num
> FROM
> ((Table1 AS act LEFT OUTER JOIN
> Table2 AS proj ON proj.Field_ID = act.Field_ID)
> LEFT OUTER JOIN Table3 AS f ON f.Field_ID = act.Field_ID) INNER JOIN
> Table4 AS cm ON cm.Contract_ID = f.Contract_ID
> ORDER BY act.Crop_Year
> with error:
> ERROR: Error in parsing of sql - Encountered " <ALL_IN_GROUP> "proj.\* "" at
> line 2, column 54.
> Was expecting one of:
> "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" ...
> <ID> ...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months