[JBoss JIRA] (TEIIDDES-2493) Check for spaces in the parent directory Flat File connection importer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2493?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2493.
----------------------------------
Resolution: Done
re-closing after target version changes
> Check for spaces in the parent directory Flat File connection importer
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-2493
> URL: https://issues.jboss.org/browse/TEIIDDES-2493
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Labels: release_notes, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0, 9.2.1
>
>
> Add a check to make sure there are no spaces in the ParentDirectory or root directory path when Flat File Connection Profile is chosen.
> ====================
> The problem is manifested on the server when attempting to query the datasource. On datasource creation, the resource adapter is written to the standalone.xml like this.
> {code:java}
> <config-property name="ParentDirectory">
> /home/mdrilling/My Dir/data
> </config-property>
> {code}
> The embedded space in the ParentDirectory property value is problematic.
> Need to determine whether to (1) disallow a path with spaces or (2) allow it, replacing the space with the appropriate control code ie {code:java} {code} - like this
> {code:java}
> <config-property name="ParentDirectory">
> /home/mdrilling/My Dir/data
> </config-property>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2745) Extension properties not imported from dynamic VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2745?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2745.
----------------------------------
Resolution: Done
re-closing after target version changes
> Extension properties not imported from dynamic VDB
> --------------------------------------------------
>
> Key: TEIIDDES-2745
> URL: https://issues.jboss.org/browse/TEIIDDES-2745
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Patch Release
> Affects Versions: 9.0.4
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0, 9.2.1
>
>
> When importing a dynamic VDB containing models with extension properties, the properties are not imported.
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <vdb name="MatViewsVdb" version="1">
> <description>For testing of materialized views</description>
>
> <model name="Source">
> <source name="Source" translator-name="h2-override"
> connection-jndi-name="java:/mat-views-ds" />
> <metadata type="DDL"><![CDATA[
>
> CREATE FOREIGN TABLE customers (
> id integer,
> name string(4000),
> address string(4000),
> CONSTRAINT PK_ID PRIMARY KEY(id)
> ) OPTIONS(NAMEINSOURCE 'customer')
>
> CREATE FOREIGN TABLE orders (
> id integer,
> customer_id integer,
> amount integer,
> CONSTRAINT PK_ID PRIMARY KEY(id),
> CONSTRAINT FK_CUST FOREIGN KEY(customer_id) REFERENCES customers(id)
> ) OPTIONS(NAMEINSOURCE 'order')
> ]]>
> </metadata>
> </model>
>
> <!-- TODO: change the CONVERTs to integer once TEIIDDES-2737 is resolved -->
> <model name="ViewModel" type="VIRTUAL">
> <metadata type="DDL"><![CDATA[
> CREATE VIEW internal_short_ttl (
> customer_id integer NOT NULL,
> total_amount integer
> ) OPTIONS (MATERIALIZED 'TRUE',
> "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'execute Source.native(''INSERT INTO check_table(id,before_load) VALUES (''internal_short_ttl'',1) ON DUPLICATE KEY UPDATE before_load=before_load+1;'');',
> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute Source.native(''INSERT INTO check_table(id,after_load) VALUES (''internal_short_ttl'',1) ON DUPLICATE KEY UPDATE after_load=after_load+1;'')'
> )
> AS /*+ cache(ttl:100)*/SELECT c.id AS customer_id, CONVERT(SUM(o.amount),biginteger) AS total_amount FROM customers c INNER JOIN orders o ON c.id = o.customer_id GROUP BY c.id;
>
> CREATE VIEW internal_long_ttl (
> customer_id integer PRIMARY KEY,
> total_amount integer
> ) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'FALSE')
> AS /*+ cache(ttl:1000 updatable)*/ SELECT c.id AS customer_id, CONVERT(SUM(o.amount),biginteger) AS total_amount FROM customers c INNER JOIN orders o ON c.id = o.customer_id GROUP BY c.id;
>
> CREATE VIEW external_long_ttl (
> customer_id integer NOT NULL,
> total_amount integer
> ) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'FALSE',
> MATERIALIZED_TABLE 'Source.DB.PUBLIC.MAT_VIEW',
> "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true',
> "teiid_rel:MATVIEW_STATUS_TABLE" 'Source.DB.PUBLIC.STATUS',
> "teiid_rel:ON_VDB_START_SCRIPT" 'exec Source.native(''MERGE INTO check_table(id,vdb_create) KEY(id) VALUES (''''external_long_ttl'''',COALESCE((SELECT vdb_create from check_table WHERE id=''''external_long_ttl''''),0)+1)'');',
> "teiid_rel:ON_VDB_DROP_SCRIPT" 'exec Source.native(''MERGE INTO check_table(id,vdb_drop) KEY(id) VALUES (''''external_long_ttl'''',COALESCE((SELECT vdb_drop from check_table WHERE id=''''external_long_ttl''''),0)+1)'');',
> "teiid_rel:MATVIEW_LOAD_SCRIPT" 'INSERT INTO mat_view_stage(customer_id,total_amount) SELECT c.id AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM customers c INNER JOIN orders o ON c.id = o.customer_id GROUP BY c.id;',
> "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'execute Source.native(''truncate table mat_view_stage'');exec Source.native(''MERGE INTO check_table(id,before_load) KEY(id) VALUES (''''external_long_ttl'''',COALESCE((SELECT before_load from check_table WHERE id=''''external_long_ttl''''),0)+1)'');',
> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'exec Source.native(''ALTER TABLE mat_view_stage RENAME TO mat_view_temp'');exec Source.native(''ALTER TABLE mat_view RENAME TO mat_view_stage'');exec Source.native(''ALTER TABLE mat_view_temp RENAME TO mat_view'');exec Source.native(''MERGE INTO check_table(id,after_load) KEY(id) VALUES (''''external_long_ttl'''',COALESCE((SELECT after_load from check_table WHERE id=''''external_long_ttl''''),0)+1)'');',
> "teiid_rel:MATVIEW_ONERROR_ACTION" 'THROW_EXCEPTION',
> "teiid_rel:MATVIEW_TTL" 2000)
> AS SELECT c.id AS customer_id, CONVERT(SUM(o.amount),biginteger) AS total_amount FROM customers c INNER JOIN orders o ON c.id = o.customer_id GROUP BY c.id;
> ]]>
> </metadata>
> </model>
> <translator name="h2-override" type="h2">
> <property name="SupportsDirectQueryProcedure" value="true" />
> </translator>
> </vdb>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2710) WS Create Operation Wizard - Creating a method with no input message
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2710?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2710.
----------------------------------
Resolution: Done
re-closing after target version changes
> WS Create Operation Wizard - Creating a method with no input message
> --------------------------------------------------------------------
>
> Key: TEIIDDES-2710
> URL: https://issues.jboss.org/browse/TEIIDDES-2710
> Project: Teiid Designer
> Issue Type: Bug
> Components: Patch Release, Web Services Support
> Affects Versions: 9.0.4
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0, 9.2.1
>
> Attachments: create-operation-dialog.png
>
>
> Coppied from BZ:
> Description of problem:
> Web service model , create operation model does not allow to create operations without input or output. Indeed it's possible to ignore warning messages and create the operation anyway. In that case wizard puts nameless and typeless messages in the schema and requires removing messages from the schema with an alternate editor.
> Version-Release number of selected component (if applicable):
>
> TD 9.0.3.Finalv2015
> How reproducible:
> Try to create a new operation in web service model
> Steps to Reproduce:
> 1. Pick one the interfaces that you have in wsdl
> 2. Create a new operation, give it a name
> 3. Try to get rid of input message, remove it's name and create
> Actual results:
> Malformed view schema
> Expected results:
> create the operation without the undesired message type
> Additional info:
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2743) Return parameter not created when importing UDF from dynamic VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2743?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2743.
----------------------------------
Resolution: Done
re-closing after target version changes
> Return parameter not created when importing UDF from dynamic VDB
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2743
> URL: https://issues.jboss.org/browse/TEIIDDES-2743
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Patch Release
> Affects Versions: 9.0.4
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0, 9.2.1
>
>
> When importing a dynamic VDB containing a UDF, the imported UDF is missing the RETURN parameter. This parameter is not specified as parameter in the DDL, but rather in the RETURNS clause.
> {code:xml}
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <vdb name="UdfProcedureVdb" version="1">
> <description />
> <property name="validationDateTime" value="Tue Nov 10 13:18:14 CET 2015" />
> <property name="validationVersion" value="8.7.1" />
> <model name="ProcedureModel" type="VIRTUAL">
> <metadata type="DDL"><![CDATA[
> CREATE VIRTUAL FUNCTION udfConcatNull (stringLeft string(4000), stringRight string(4000)) RETURNS string OPTIONS("FUNCTION-CATEGORY" 'MY_TESTING_FUNCTION_CATEGORY', JAVA_CLASS 'userdefinedfunctions.MyConcatNull', JAVA_METHOD 'myConcatNull')
> ]]></metadata>
> </model>
> </vdb>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2767) Illegal argument exception if explorer context menu launched prior to explorer view fully functional
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2767?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2767.
----------------------------------
Resolution: Done
re-closing after target version changes
> Illegal argument exception if explorer context menu launched prior to explorer view fully functional
> ----------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2767
> URL: https://issues.jboss.org/browse/TEIIDDES-2767
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0, 9.2.1
>
>
> Re-opening a workspace with projects and larger model sets will take a little longer to launch.
> Right-clicking on the explorer may throw the following because Model Explorer is adding a listener that calls fillContextMenu() on it's own. Need to check that ModelerActionService is fully added/functional.
> org.eclipse.core.runtime.AssertionFailedException: null argument:Action must not be null
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
> at org.eclipse.jface.action.ContributionManager.add(ContributionManager.java:76)
> at org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator.createRefactorMenu(ModelExplorerResourceNavigator.java:1206)
> at org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator.fillContextMenu(ModelExplorerResourceNavigator.java:1291)
> at org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator$13.menuAboutToShow(ModelExplorerResourceNavigator.java:1144)
> at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:352)
> at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:492)
> at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:487)
> at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:519)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1393)
> at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:198)
> at org.eclipse.swt.widgets.Display.runPopups(Display.java:3841)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3399)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2762) REST import parameter issue - problem on java 8
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2762?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2762.
----------------------------------
Resolution: Done
re-closing after target version changes
> REST import parameter issue - problem on java 8
> -----------------------------------------------
>
> Key: TEIIDDES-2762
> URL: https://issues.jboss.org/browse/TEIIDDES-2762
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.5
> Reporter: Matus Makovy
> Assignee: Ted Jones
> Priority: Blocker
> Labels: verified_jbdsis-8.0.5
> Fix For: 10.0, 9.0.5, 9.2.1
>
> Attachments: Screen Shot 2016-01-15 at 11.41.18.png
>
>
> I discovered this on 9.0.5, but the issue seems to be caused by Java 8, so it doesn't matter which version of TD is used.
> I tried to import data from REST ws and when I added some parameter (name of parameter is "new") I got following error:
> {code:java}
> Illegal character(s) in message header field: rest_param:new
> {code}
> This seems to be problem only with Java 8. It works with Java 7.
> Marked this as blocker, because user cannot import from REST if he wants to use some parameters during import. After some googling I found out that this could be an issue in Java not in Designer.
> Java version: 1.8.0_65, vendor: Oracle Corporation
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2775) Provide automated way to convert a old functional model into relational model
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2775?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2775.
----------------------------------
Resolution: Done
re-closing after target version changes
> Provide automated way to convert a old functional model into relational model
> -----------------------------------------------------------------------------
>
> Key: TEIIDDES-2775
> URL: https://issues.jboss.org/browse/TEIIDDES-2775
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Migration, Modeling, Patch Release, Usability
> Affects Versions: 9.0.3
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
> Labels: release_notes, verified_jbdsis-8.0.6, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0, 9.0.6
>
> Attachments: convert-functions-to-procedures-action.png, convert-functions-to-procedures-dialog.png, converted-functions-to-procedures-diagram.png
>
>
> The primary stipulation is that it will no longer be supported from a design time perspective the ability to create the function model. Consider offering option of an automated utility of some kind for this migration. There is a manual workaround, but for the user and usability, we should do this for them.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2783) Need to add support for parsing OPTIONS in procedure statements
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2783?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2783.
----------------------------------
Resolution: Done
re-closing after target version changes
> Need to add support for parsing OPTIONS in procedure statements
> ---------------------------------------------------------------
>
> Key: TEIIDDES-2783
> URL: https://issues.jboss.org/browse/TEIIDDES-2783
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, ModeShape Integration, Patch Release
> Reporter: Barry LaFond
> Assignee: Dan Florian
> Labels: release_notes, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0
>
>
> The procedure DDL syntax supports OPTIONS() clause for procedure, parameter, result set, result set columns and datatype (RETURNS) clause.
> CreateProcedureParser.parseReturnsClause() is not processing any OPTIONS() for procedure when RETURNS is just a datatype. See: https://docs.jboss.org/author/display/TEIID/BNF+for+SQL+Grammar#BNFforSQL...
> Should be able to parse the following and set the EMF *Description* (Annotation) value when imported into Designer
> {code}
> CREATE FOREIGN PROCEDURE ProcedureWithRS (
> newParameter_1 string(4000) OPTIONS(ANNOTATION 'parameter 1 description'),
> newParameter_2 string(4000)
> ) RETURNS string(255) OPTIONS(ANNOTATION 'Example')
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2589) The model extension definition "relational" found in model is a different version than the one in the registry.
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2589?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2589.
----------------------------------
Resolution: Done
re-closing after target version changes
> The model extension definition "relational" found in model is a different version than the one in the registry.
> ---------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2589
> URL: https://issues.jboss.org/browse/TEIIDDES-2589
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Affects Versions: 9.0, 9.0.1, 9.1, 9.0.2
> Reporter: Lukas Mro
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0, 9.2.1
>
>
> After importing model from TD 8.1.0 to 9.X.X two types of errors occures
> 3 types of errors occures:
> 1. The model extension definition "rest" found in model is not registered in workspace -> this one can be autofix
> 2. The model extension definition "relational" found in model is a different version than the one in the registry -> This one do not have fix
> 3. java.lang.StringIndexOutOfBoundsException: String index out of range: 1
> -> this one do not have fix
> I`m not sure what should i send you, AMA :)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months