[JBoss JIRA] (TEIIDDES-1164) CLONE - Index metadata should not treat cardinality 0 as unknown
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1164?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-1164:
------------------------------------------
You are defaulting table cardinality to 0 to mean unknown, when 0 is actually a valid value. So if you change the model default to -1, then you would also change the RuntimeAdapter index version to the next number, which I believe should be 10 to let the engine know that prior versions with the 0 value should still be treated as unknown.
> CLONE - Index metadata should not treat cardinality 0 as unknown
> ----------------------------------------------------------------
>
> Key: TEIIDDES-1164
> URL: https://issues.jboss.org/browse/TEIIDDES-1164
> Project: Teiid Designer
> Issue Type: Quality Risk
> Components: Teiid Integration
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Assignee: Paul Richardson
> Fix For: 8.1
>
>
> The default cardinality is currently 0, which is treated as unknown, however it would be better if the default were something like -1 instead. This will require introducing a new index file version (so that older vdbs with a value of 0 can be understood as meaning unknown) and updating the teiid/designer metadata defaults for cardinality as -1.
--
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, 12 months
[JBoss JIRA] (TEIIDDES-363) Add the option in Validation Preferences for 'cross-join'
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-363?page=com.atlassian.jira.plug... ]
Barry LaFond commented on TEIIDDES-363:
---------------------------------------
The SQL Transformation Validation framework needs some investigation. Currently (version 8.1 development), the Empty SQL validation check (with preference) is not performed due to the SQL validation being prevented with a USER SQL == NULL check in SqlMappingRootCache.createStatus() method.
This cross-join preference should be added as a check in SqlTransformationMappingRootValidationRule.java
> Add the option in Validation Preferences for 'cross-join'
> ---------------------------------------------------------
>
> Key: TEIIDDES-363
> URL: https://issues.jboss.org/browse/TEIIDDES-363
> Project: Teiid Designer
> Issue Type: Feature Request
> Reporter: Debbie Steigner
> Assignee: Paul Richardson
> Fix For: 8.1
>
>
> Add option to ignore the cross-join warning.
--
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, 12 months
[JBoss JIRA] (TEIIDDES-1164) CLONE - Index metadata should not treat cardinality 0 as unknown
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1164?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1164:
----------------------------------------
Steve, can you be more specific about what object in Designer needs default to -1? and what/where is the "index version"?
Assuming it's versioning the Index Files?
I see a method in our RuntimeAdapter...
protected static void appendIndexVersion( final int indexVersion,
final StringBuffer sb ) {
// The range of index versions is [0,99]
CoreArgCheck.isTrue(indexVersion > -1 && indexVersion < 100, "Index version " + indexVersion + " out of range. (0 - 99)"); //$NON-NLS-1$ //$NON-NLS-2$
sb.append(IndexConstants.RECORD_STRING.INDEX_VERSION_MARKER);
if (indexVersion < 10) {
sb.append(Integer.toString(0));
sb.append(Integer.toString(indexVersion));
} else {
sb.append(Integer.toString(indexVersion));
}
}
> CLONE - Index metadata should not treat cardinality 0 as unknown
> ----------------------------------------------------------------
>
> Key: TEIIDDES-1164
> URL: https://issues.jboss.org/browse/TEIIDDES-1164
> Project: Teiid Designer
> Issue Type: Quality Risk
> Components: Teiid Integration
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Assignee: Paul Richardson
> Fix For: 8.1
>
>
> The default cardinality is currently 0, which is treated as unknown, however it would be better if the default were something like -1 instead. This will require introducing a new index file version (so that older vdbs with a value of 0 can be understood as meaning unknown) and updating the teiid/designer metadata defaults for cardinality as -1.
--
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, 12 months
[JBoss JIRA] (TEIIDDES-1554) Unable to validate transformation in project set in Designer 8 where the project was built in Designer 7.x
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1554?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1554.
------------------------------------
Resolution: Rejected
The project contained a bogus model that, when recreated eliminated the original validation problems.
It also raised a migration issue with new Teiid validation around using TEMPORARY TABLE in SQL statement
> Unable to validate transformation in project set in Designer 8 where the project was built in Designer 7.x
> ----------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1554
> URL: https://issues.jboss.org/browse/TEIIDDES-1554
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations, Validation
> Affects Versions: 8.0
> Environment: jbdevstudio-product-universal-6.0.0.GA-v20121206-1855-B186.jar
> Designer 8 final release
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 8.1
>
> Attachments: portfolio.zip
>
>
> Taking a project set built in the latest JDBS 5 / Designer 7.x and trying to validate it in Designer 8.
> The MartketDataView.StockPrices view has this error:
> Found problems validating transformation defining MarketDataView/StockPrices, re-validate in the transformation editor.
> Unable to to get the error to go away after revalidating. Also tried the quick fix with no luck. Also tried typing in spaces to trigger revalidation, no luck.
> No error messages in the .log. Attached the project set.
--
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, 12 months
[JBoss JIRA] (TEIIDDES-1554) Unable to validate transformation in project set in Designer 8 where the project was built in Designer 7.x
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1554?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-1554 at 1/24/13 5:12 PM:
-----------------------------------------------------------------
The portfolio.zip project set which contains a 3.8 MB MarketDataView.xmi file which has only one table in it. Somehow overe 17,000 extra/redundant/bogus SqlTransformationMappingRoot (EMF) objects were created in this model. Only the first one is valid, and the rest don't have enough info attached to them to validate any more than: "Re-validate in the transformation editor.... blah, blah.."
I recreated/replaced the MarketDataView model and it's StockPrices table containing the same SQL statement and it validated fine.
I also cleared out 2 transformations in the Stocks view model, so it would find the new MarketDataView.StockPrices table. There was one remaining validation error on the StockValidation virtual procedure:
===>>> ERROR: TEIID30118 Cannot create temporary table "TEMP". An object with the same name already exists.
So the procedure below needs to be tweaked based on the new Teiid TEMPORARY TABLE syntax/rules and described in the next Teiid Release Documenation
CREATE VIRTUAL PROCEDURE
BEGIN
DECLARE String VARIABLES.msg;
CREATE LOCAL TEMPORARY TABLE TEMP (companyname string, symbol string, price bigdecimal, message string);
LOOP ON (SELECT
Stock.Stock.symbol, Stock.Stock.price, Stock.Stock.COMPANY_NAME
FROM
Stock) AS txncursor
BEGIN
VARIABLES.msg = RulesUDF.ValidateMarket(txncursor.COMPANY_NAME, txncursor.symbol, txncursor.price);
IF(VARIABLES.msg <> 'NoMsg')
BEGIN
INSERT INTO TEMP (TEMP.companyname, TEMP.symbol, TEMP.price, TEMP.message) VALUES (txncursor.COMPANY_NAME, txncursor.symbol, txncursor.price, VARIABLES.msg);
END
END
SELECT TEMP.companyname, TEMP.symbol, TEMP.price, TEMP.message FROM TEMP;
END
was (Author: blafond):
The portfolio.zip project set which contains a 3.8 MB MarketDataView.xmi file which has only one table in it. Somehow overe 17,000 extra/redundant/bogus SqlTransformationMappingRoot (EMF) objects were created in this model. Only the first one is valid, and the rest don't have enough info attached to them to validate any more than: "Re-validate in the transformation editor.... blah, blah.."
I recreated/replaced the MarketDataView model and it's StockPrices table containing the same SQL statement and it validated fine.
I also cleared out 2 transformations in the Stocks view model, so it would find the new MarketDataView.StockPrices table. There was one remaining validation error on the StockValidation virtual procedure:
===>>> ERROR: TEIID30118 Cannot create temporary table "TEMP". An object with the same name already exists.
So the procedure below needs to be tweaked based on the new Teiid TEMPORARY TABLE syntax/rules
CREATE VIRTUAL PROCEDURE
BEGIN
DECLARE String VARIABLES.msg;
CREATE LOCAL TEMPORARY TABLE TEMP (companyname string, symbol string, price bigdecimal, message string);
LOOP ON (SELECT
Stock.Stock.symbol, Stock.Stock.price, Stock.Stock.COMPANY_NAME
FROM
Stock) AS txncursor
BEGIN
VARIABLES.msg = RulesUDF.ValidateMarket(txncursor.COMPANY_NAME, txncursor.symbol, txncursor.price);
IF(VARIABLES.msg <> 'NoMsg')
BEGIN
INSERT INTO TEMP (TEMP.companyname, TEMP.symbol, TEMP.price, TEMP.message) VALUES (txncursor.COMPANY_NAME, txncursor.symbol, txncursor.price, VARIABLES.msg);
END
END
SELECT TEMP.companyname, TEMP.symbol, TEMP.price, TEMP.message FROM TEMP;
END
> Unable to validate transformation in project set in Designer 8 where the project was built in Designer 7.x
> ----------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1554
> URL: https://issues.jboss.org/browse/TEIIDDES-1554
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations, Validation
> Affects Versions: 8.0
> Environment: jbdevstudio-product-universal-6.0.0.GA-v20121206-1855-B186.jar
> Designer 8 final release
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 8.1
>
> Attachments: portfolio.zip
>
>
> Taking a project set built in the latest JDBS 5 / Designer 7.x and trying to validate it in Designer 8.
> The MartketDataView.StockPrices view has this error:
> Found problems validating transformation defining MarketDataView/StockPrices, re-validate in the transformation editor.
> Unable to to get the error to go away after revalidating. Also tried the quick fix with no luck. Also tried typing in spaces to trigger revalidation, no luck.
> No error messages in the .log. Attached the project set.
--
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, 12 months
[JBoss JIRA] (TEIIDDES-1554) Unable to validate transformation in project set in Designer 8 where the project was built in Designer 7.x
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1554?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1554:
----------------------------------------
The portfolio.zip project set which contains a 3.8 MB MarketDataView.xmi file which has only one table in it. Somehow overe 17,000 extra/redundant/bogus SqlTransformationMappingRoot (EMF) objects were created in this model. Only the first one is valid, and the rest don't have enough info attached to them to validate any more than: "Re-validate in the transformation editor.... blah, blah.."
I recreated/replaced the MarketDataView model and it's StockPrices table containing the same SQL statement and it validated fine.
I also cleared out 2 transformations in the Stocks view model, so it would find the new MarketDataView.StockPrices table. There was one remaining validation error on the StockValidation virtual procedure:
===>>> ERROR: TEIID30118 Cannot create temporary table "TEMP". An object with the same name already exists.
So the procedure below needs to be tweaked based on the new Teiid TEMPORARY TABLE syntax/rules
CREATE VIRTUAL PROCEDURE
BEGIN
DECLARE String VARIABLES.msg;
CREATE LOCAL TEMPORARY TABLE TEMP (companyname string, symbol string, price bigdecimal, message string);
LOOP ON (SELECT
Stock.Stock.symbol, Stock.Stock.price, Stock.Stock.COMPANY_NAME
FROM
Stock) AS txncursor
BEGIN
VARIABLES.msg = RulesUDF.ValidateMarket(txncursor.COMPANY_NAME, txncursor.symbol, txncursor.price);
IF(VARIABLES.msg <> 'NoMsg')
BEGIN
INSERT INTO TEMP (TEMP.companyname, TEMP.symbol, TEMP.price, TEMP.message) VALUES (txncursor.COMPANY_NAME, txncursor.symbol, txncursor.price, VARIABLES.msg);
END
END
SELECT TEMP.companyname, TEMP.symbol, TEMP.price, TEMP.message FROM TEMP;
END
> Unable to validate transformation in project set in Designer 8 where the project was built in Designer 7.x
> ----------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1554
> URL: https://issues.jboss.org/browse/TEIIDDES-1554
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations, Validation
> Affects Versions: 8.0
> Environment: jbdevstudio-product-universal-6.0.0.GA-v20121206-1855-B186.jar
> Designer 8 final release
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 8.1
>
> Attachments: portfolio.zip
>
>
> Taking a project set built in the latest JDBS 5 / Designer 7.x and trying to validate it in Designer 8.
> The MartketDataView.StockPrices view has this error:
> Found problems validating transformation defining MarketDataView/StockPrices, re-validate in the transformation editor.
> Unable to to get the error to go away after revalidating. Also tried the quick fix with no luck. Also tried typing in spaces to trigger revalidation, no luck.
> No error messages in the .log. Attached the project set.
--
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, 12 months
[JBoss JIRA] (TEIIDDES-1308) Develop suite of Migration utilities for deprecated metamodels
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1308?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1308:
-----------------------------------
Description:
Several metamodels were retired or deprecated since Metamatrix went Open Source.
In 8.0 we'll be left with the following supported primary metamodels
* Relational (Source and View)
* XML Document (View)
* Web Services (View)
* XML Schema (XSD)
* Function
* Extension
Metamodels being officially retired are:
* Relationship
* XML Service (Source and View)
* UML
Only Function and Extension metamodels will be migrated to newer Teiid Designer constructs
* Function Models will be converted to Source or View Procedures
* Extension Models will be converted to new MED (Model Extension Definition) framework
Subtasks will be defined to cover this work in more detail
was:
Several metamodels were retired or deprecated since Metamatrix went Open Source.
In 8.0 we'll be left with the following supported primary metamodels
* Relational (Source and View)
* XML Document (View)
* Web Services (View)
* XML Schema (XSD)
Metamodels being officially retired are:
* Function
* Extension
* Relationship
* XML Service (Source and View)
* UML
Only Function and Extension metamodels will be migrated to newer Teiid Designer constructs
* Function Models will be converted to Source or View Procedures
* Extension Models will be converted to new MED (Model Extension Definition) framework
Subtasks will be defined to cover this work in more detail
> Develop suite of Migration utilities for deprecated metamodels
> --------------------------------------------------------------
>
> Key: TEIIDDES-1308
> URL: https://issues.jboss.org/browse/TEIIDDES-1308
> Project: Teiid Designer
> Issue Type: Task
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.1
>
>
> Several metamodels were retired or deprecated since Metamatrix went Open Source.
> In 8.0 we'll be left with the following supported primary metamodels
> * Relational (Source and View)
> * XML Document (View)
> * Web Services (View)
> * XML Schema (XSD)
> * Function
> * Extension
> Metamodels being officially retired are:
> * Relationship
> * XML Service (Source and View)
> * UML
> Only Function and Extension metamodels will be migrated to newer Teiid Designer constructs
> * Function Models will be converted to Source or View Procedures
> * Extension Models will be converted to new MED (Model Extension Definition) framework
> Subtasks will be defined to cover this work in more detail
--
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, 12 months
[JBoss JIRA] (TEIIDDES-1308) Develop suite of Migration utilities for deprecated metamodels
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1308?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1308:
-----------------------------------
Fix Version/s: Future
(was: 8.1)
> Develop suite of Migration utilities for deprecated metamodels
> --------------------------------------------------------------
>
> Key: TEIIDDES-1308
> URL: https://issues.jboss.org/browse/TEIIDDES-1308
> Project: Teiid Designer
> Issue Type: Task
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: Future
>
>
> Several metamodels were retired or deprecated since Metamatrix went Open Source.
> In 8.0 we'll be left with the following supported primary metamodels
> * Relational (Source and View)
> * XML Document (View)
> * Web Services (View)
> * XML Schema (XSD)
> * Function
> * Extension
> Metamodels being officially retired are:
> * Relationship
> * XML Service (Source and View)
> * UML
> Only Function and Extension metamodels will be migrated to newer Teiid Designer constructs
> * Function Models will be converted to Source or View Procedures
> * Extension Models will be converted to new MED (Model Extension Definition) framework
> Subtasks will be defined to cover this work in more detail
--
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, 12 months
[JBoss JIRA] (TEIIDDES-1523) Source Function And Procedure Modeling And Terminology Is Confusing
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1523?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1523.
------------------------------------
Resolution: Done
Added Result Set tab with applicable widgets for creating/editing result set
> Source Function And Procedure Modeling And Terminology Is Confusing
> -------------------------------------------------------------------
>
> Key: TEIIDDES-1523
> URL: https://issues.jboss.org/browse/TEIIDDES-1523
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.8
> Reporter: Dan Florian
> Assignee: Barry LaFond
> Fix For: 8.1
>
> Attachments: new-procedure-wizard-parameters.png, new-procedure-wizard-properties.png, new-procedure-wizard-resultset.png
>
>
> It is very confusing that creating a "Source Function" and creating a "Procedure" both end up with model objects of type "Procedure." The source function wizard sets a procedure's "function" property to "true" and requires the user to create one or more inputs and one output. However, after finishing the wizard, the user is free to delete the inputs, delete the output, and set the "function" property to "false" if they so choose (in essence making it just a procedure). Alternatively, the user could start by creating a procedure, then set the "function" property to "true," add one or more inputs, add an output, and end up creating a "source function." Maybe the source function wizard could be adapted and used when creating procedures.
--
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, 12 months