[JBoss JIRA] (TEIIDDES-1709) Unable to import relational model from xml
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created TEIIDDES-1709:
-------------------------------------------
Summary: Unable to import relational model from xml
Key: TEIIDDES-1709
URL: https://issues.jboss.org/browse/TEIIDDES-1709
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 8.1
Reporter: Andrej Podhradsky
Unable to import relational model from xml file. During the importing you can see that File Contents is still empty in the wizard (I think there is the problem). After importing the created xmi file is empty.
--
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, 2 months
[JBoss JIRA] (TEIIDDES-1667) Ability to define UDF with vararg to be used in a static VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1667?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1667:
----------------------------------------
* Created a Scalar Function : makeList()
** items : object
** Return Parameter : object
* Set VARARGS extension property to TRUE
* Created Virtual table named TestSimpleUDF
** one column > myListObject : object
* Set transformation to: SELECT MAKELIST('1', '2') AS myListObject
Get following transformation error:
ERROR: TEIID30068 The function 'MAKELIST('1', '2')' is an unknown form. Check that the function name and number of arguments is correct.
If I limit it to MAKELIST('1') in the SQL it's fine, but more than one arg it fails validation.
> Ability to define UDF with vararg to be used in a static VDB
> ------------------------------------------------------------
>
> Key: TEIIDDES-1667
> URL: https://issues.jboss.org/browse/TEIIDDES-1667
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.0
> Environment: JBoss AS 7.1.1
> Teiid 8.3.0
> Teiid Designer 8.0.0
> Reporter: Shakir Shaik
> Assignee: Mark Drilling
> Fix For: 8.2
>
>
> I am not able to use a UDF with vararg and deploy the same in a static VDB.
> Please see the details in the following thread of Teiid Designer User forum discussions:
> https://community.jboss.org/thread/223823?tstart=0
--
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, 2 months
[JBoss JIRA] (TEIIDDES-1667) Ability to define UDF with vararg to be used in a static VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1667?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1667:
----------------------------------------
Created the following UDF java class:
{code}
package org.me.functions;
import java.util.ArrayList;
import java.util.Collections;
import java.util.List;
public class MyMathFunctions {
public static Object makeList(Object... items) {
if (items[0] instanceof Double) {
List<Double> returnList = new ArrayList<Double>();
for (Object item : items) {
returnList.add((Double)item);
}
return returnList;
} else if (items[0] instanceof Float) {
List<Float> returnList = new ArrayList<Float>();
for (Object item : items) {
returnList.add((Float)item);
}
return returnList;
}
return Collections.EMPTY_LIST;
}
}
{code}
> Ability to define UDF with vararg to be used in a static VDB
> ------------------------------------------------------------
>
> Key: TEIIDDES-1667
> URL: https://issues.jboss.org/browse/TEIIDDES-1667
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.0
> Environment: JBoss AS 7.1.1
> Teiid 8.3.0
> Teiid Designer 8.0.0
> Reporter: Shakir Shaik
> Assignee: Mark Drilling
> Fix For: 8.2
>
>
> I am not able to use a UDF with vararg and deploy the same in a static VDB.
> Please see the details in the following thread of Teiid Designer User forum discussions:
> https://community.jboss.org/thread/223823?tstart=0
--
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, 2 months
[JBoss JIRA] (TEIIDDES-1693) Table name "product:info: being imported as "product}info" through new Teiid Connection importer
by Dan Florian (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1693?page=com.atlassian.jira.plu... ]
Dan Florian commented on TEIIDDES-1693:
---------------------------------------
The invalid name is coming from the ModeShape DDL sequencer. The ModeShape Teiid DDL parser is interpreting the ':' in the identifier as if the identifier is of the form "namespacePrefix:name." The actual, or full name, of the object in ModeShape/JCR has the form "{namespaceUrl}name." A lookup is done to find the "namespaceUrl" using the "namespacePrefix."
In this case, the ModeShape Teiid parser tries to look up the namespace URL for the "Products.product" prefix and does not find one. The parser then *assumes* that the part of the identifier before the ':' is the URL itself and then inserts curly braces around it when forming the full name. So "Products.product:info" becomes "{Products.product}info".
Since the Teiid DDL actually allows a similar "namespace:identifier" format via their "option namespace" DDL statement, I'm not sure what the solution is right now.
> Table name "product:info: being imported as "product}info" through new Teiid Connection importer
> ------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1693
> URL: https://issues.jboss.org/browse/TEIIDDES-1693
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Dan Florian
> Fix For: 8.2
>
>
> MY SQL Source: jdbc:mysql://slntds03.mw.lab.eng.bos.redhat.com:3306/Products
> This DB defines a table as "product:info"
> JDBC importer correctly imports that table as "product_info"
> Teiid Connection importer changes the name to "product}info" and the columns names end up as "{PRODUCT}ID instead of "PRODUCT_ID"
--
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, 2 months
[JBoss JIRA] (TEIIDDES-1670) DDL Importer - problem with re-import when setting descriptions
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1670?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1670:
----------------------------------------
Looks like the differences map stored in the difference processor is attaching the *description* change (by it's 'feature ID') to the Base Table. When the Base Table is processed, it blindly walks through the set of changes, grabs the *feature* and executes a property change. In this instance the *CorePackage.ANNOTATION__DESCRIPTION* == *RelationalPackage.BASE_TABLE__NAME* so the name gets replaced or set incorrectly.
So, because this is not working at ALL, I think we should remove the "check-box" until we can get to fixing this JIRA and find the right way to set/track/change Descriptions on EObjects.
> DDL Importer - problem with re-import when setting descriptions
> ---------------------------------------------------------------
>
> Key: TEIIDDES-1670
> URL: https://issues.jboss.org/browse/TEIIDDES-1670
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.1
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 8.2
>
>
> When using the DDL importer for an existing model (update), the model entity names are getting reset. This only seems to occur if 'set description of Model Entities to corresponding DDL statement' checkbox is checked. The Entity names get changed to the default name of the entity.
--
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, 2 months
[JBoss JIRA] (TEIIDDES-1707) Data Source Created Using Model Connection Info Does Not Work
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1707?page=com.atlassian.jira.plu... ]
Mark Drilling commented on TEIIDDES-1707:
-----------------------------------------
If you create a connection profile (for example MySQL), the URL pre-populates with jdbc:mysql://localhost:3306/database. It appears that in the Connection Profile wizard, you can drop the database name and the Test Connection will still succeed. Then later when you use the connection profile, the URL without the /database gets picked up but then it fails when attempting to use it.
> Data Source Created Using Model Connection Info Does Not Work
> -------------------------------------------------------------
>
> Key: TEIIDDES-1707
> URL: https://issues.jboss.org/browse/TEIIDDES-1707
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.1
> Reporter: Dan Florian
>
> I did a JDBC import that created a relational model. I right-clicked on the new model and Modeling > Create Data Source. On the Create Data Source dialog I entered a data source name and left every other value untouched. I had to enter a password after that dialog closed. Using the newly created data source in a Teiid Connection import fails because the URL of the data source does not have the database name.
--
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, 2 months
[JBoss JIRA] (TEIIDDES-1708) Delete Data Source in ServerView causes tree to collapse
by Mark Drilling (JIRA)
Mark Drilling created TEIIDDES-1708:
---------------------------------------
Summary: Delete Data Source in ServerView causes tree to collapse
Key: TEIIDDES-1708
URL: https://issues.jboss.org/browse/TEIIDDES-1708
Project: Teiid Designer
Issue Type: Enhancement
Components: Views
Affects Versions: 8.1
Reporter: Mark Drilling
In the Designer server view, deletion of a datasource causes the tree to collapse.
In the server view, start the server. Under Teiid Server Configuration, expand the Data Sources folder to show all the sources. When you delete one of the data sources, the DataSources folder collapses. It would be preferable to maintain the open state.
--
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, 2 months