[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: 8.7
8.6.1
(was: 8.6)
> '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
> Security Level: Public(Everyone can see)
> Components: VDB & Execution
> Affects Versions: 8.3.1
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 8.7, 8.6.1
>
>
> 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.1#6329)
11 years, 7 months
[JBoss JIRA] (TEIIDDES-2187) Teiid Connection importer- chosing a location isn't filled in unless you hit back button
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2187?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2187:
-----------------------------------
Fix Version/s: 8.7
8.6.1
(was: 8.6)
> Teiid Connection importer- chosing a location isn't filled in unless you hit back button
> ----------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2187
> URL: https://issues.jboss.org/browse/TEIIDDES-2187
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Import/Export
> Affects Versions: 8.3.2
> Environment: Windows Vista or 2008 Only
> Reporter: Debbie Steigner
> Assignee: Mark Drilling
> Fix For: 8.7, 8.6.1
>
>
> This only happens when installed on Windows Vista or 2008 not on Linux.
> Choose File -> Import -> Teiid Designer -> Teiid Connection >> Source model:
> Then, choose a particular data source (shouldn't matter which one)
> Click "Next", this screen will now ask you to choose a location
> Click on the dots behind the grayed out "Location:" field and choose a location
> After selecting a location and pressing the "Ok" button, the location is not taken from the "Select a folder" dialog box and therefore empty.
> If I now choose "Back", I arrive in the previous screen again. Pressing "Next" again now does fill in the previously chosen "Location" value.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (TEIIDDES-2286) Creating procedure and assigning results works different depending on steps taken
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2286?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2286:
----------------------------------------
The New Procedure wizards do not push the parameter types down to the result set. The default datatype is "string", so that may have been how you interpreted it. Without that behavior, I'm not seeing enough of a difference in the use-cases to warrent this a bug or enhancement.
If you can atttach more defined steps and screen caps, maybe I could see what you are seeing.
> Creating procedure and assigning results works different depending on steps taken
> ---------------------------------------------------------------------------------
>
> Key: TEIIDDES-2286
> URL: https://issues.jboss.org/browse/TEIIDDES-2286
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Dialogs
> Affects Versions: 8.5.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
>
> Trying to create a relational view procedure. And in the wizard, if I do NOT enter a result set, and click OK, and then proceed to right click on procedure to add result set (but add no column), the result set ends up taking on the datatype that the procedure returns. However, if in the wizard, I add the name of the result set (same name used if right mouse clicking above) and do not add a column, it doesn't work the same.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (TEIIDDES-2286) Creating procedure and assigning results works different depending on steps taken
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2286?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2286:
-----------------------------------
Fix Version/s: (was: 8.6)
> Creating procedure and assigning results works different depending on steps taken
> ---------------------------------------------------------------------------------
>
> Key: TEIIDDES-2286
> URL: https://issues.jboss.org/browse/TEIIDDES-2286
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Dialogs
> Affects Versions: 8.5.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
>
> Trying to create a relational view procedure. And in the wizard, if I do NOT enter a result set, and click OK, and then proceed to right click on procedure to add result set (but add no column), the result set ends up taking on the datatype that the procedure returns. However, if in the wizard, I add the name of the result set (same name used if right mouse clicking above) and do not add a column, it doesn't work the same.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (TEIIDDES-2316) Excel import creates wrong datatype for ROW_ID column
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2316?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-2316:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1134006|https://bugzilla.redhat.com/show_bug.cgi?id=1134006] from NEW to MODIFIED
> Excel import creates wrong datatype for ROW_ID column
> -----------------------------------------------------
>
> Key: TEIIDDES-2316
> URL: https://issues.jboss.org/browse/TEIIDDES-2316
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Import/Export, Modeling, Teiid Integration
> Affects Versions: 8.6
> Environment: Teiid Designer 8.6.0.Alpha1
> Teiid 8.7.1
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Fix For: 8.6
>
>
> Following https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable (Option 1 using Teiid Designer), the imported model has the ROW_ID column modeled with datatype "integer", which results in BigInteger runtime datatype. After adding this model to a vdb and deploying, the following queries work ok:
> {code:sql}
> SELECT * FROM Sheet1
> SELECT * FROM Sheet1 WHERE row_id > 2
> {code}
> but the following query fails:
> {code:sql}
> SELECT * FROM Sheet1 WHERE row_id = 2
> {code}
> The error is
> bq. org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidException: java.math.BigInteger cannot be cast to java.lang.Integer
> After changing the datatype to "int : xs:long" and redeploying, the above query works as expected.
> However, if I copy the generated dynamic vdb (attached) and deploy it on the server (without using Designer), running the query against that works.
> The DDL for import is
> {code:sql}
> SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel;
> CREATE FOREIGN TABLE Sheet1 (
> ROW_ID integer OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_excel:CELL_NUMBER" 'ROW_ID'),
> FirstName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '1'),
> LastName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '2'),
> Age double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '3'),
> CONSTRAINT PK0 PRIMARY KEY(ROW_ID)
> ) OPTIONS ("teiid_excel:FILE" 'names.xlsx', "teiid_excel:FIRST_DATA_ROW_NUMBER" '2');
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (TEIIDDES-2256) Confusing data type "integer" and "int"
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2256?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2256.
------------------------------------
Resolution: Done
TEIIDDES-2256, TEIIDDES-2316
* redirected integer type to integer base type instead of biginteger
* Fix DDL datatype processor to convert "integer" types to int
* removed integer from selection in Set Datatype Dialog
* Added base-type and design-time type columns to Set Datatype Dialog
* changed Relational Table and Procedure Editors to use built-in types instead of design time types to be consistent
master commit: https://github.com/Teiid-Designer/teiid-designer/commit/5c417a9d2d31deb02...
> Confusing data type "integer" and "int"
> ---------------------------------------
>
> Key: TEIIDDES-2256
> URL: https://issues.jboss.org/browse/TEIIDDES-2256
> Project: Teiid Designer
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Import/Export
> Affects Versions: 8.6
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.6
>
> Attachments: builtin-types.xsd, full-datatypes-1.png, full-datatypes-2.png, set-datatype-dialog.png, set-datatype-dialog_3.png
>
>
> I understand that
> "integer" maps to "xs:biginteger"
> "int" maps "xs:long"
> How they are confusing when there is already one available for biginteger. Also the Table creation wizard does not provide option to to select "int". When user chooses "integer" it often is "int".
> This confusion needs to be resolved. IMO "integer" can be removed, however I am not sure how it effects data type system
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (TEIIDDES-2316) Excel import creates wrong datatype for ROW_ID column
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2316?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2316.
------------------------------------
Resolution: Done
TEIIDDES-2256, TEIIDDES-2316
* redirected integer type to integer base type instead of biginteger
* Fix DDL datatype processor to convert "integer" types to int
* removed integer from selection in Set Datatype Dialog
* Added base-type and design-time type columns to Set Datatype Dialog
* changed Relational Table and Procedure Editors to use built-in types instead of design time types to be consistent
master commit: https://github.com/Teiid-Designer/teiid-designer/commit/5c417a9d2d31deb02...
> Excel import creates wrong datatype for ROW_ID column
> -----------------------------------------------------
>
> Key: TEIIDDES-2316
> URL: https://issues.jboss.org/browse/TEIIDDES-2316
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Import/Export, Modeling, Teiid Integration
> Affects Versions: 8.6
> Environment: Teiid Designer 8.6.0.Alpha1
> Teiid 8.7.1
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Fix For: 8.6
>
>
> Following https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable (Option 1 using Teiid Designer), the imported model has the ROW_ID column modeled with datatype "integer", which results in BigInteger runtime datatype. After adding this model to a vdb and deploying, the following queries work ok:
> {code:sql}
> SELECT * FROM Sheet1
> SELECT * FROM Sheet1 WHERE row_id > 2
> {code}
> but the following query fails:
> {code:sql}
> SELECT * FROM Sheet1 WHERE row_id = 2
> {code}
> The error is
> bq. org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidException: java.math.BigInteger cannot be cast to java.lang.Integer
> After changing the datatype to "int : xs:long" and redeploying, the above query works as expected.
> However, if I copy the generated dynamic vdb (attached) and deploy it on the server (without using Designer), running the query against that works.
> The DDL for import is
> {code:sql}
> SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel;
> CREATE FOREIGN TABLE Sheet1 (
> ROW_ID integer OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_excel:CELL_NUMBER" 'ROW_ID'),
> FirstName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '1'),
> LastName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '2'),
> Age double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '3'),
> CONSTRAINT PK0 PRIMARY KEY(ROW_ID)
> ) OPTIONS ("teiid_excel:FILE" 'names.xlsx', "teiid_excel:FIRST_DATA_ROW_NUMBER" '2');
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (TEIIDDES-2316) Excel import creates wrong datatype for ROW_ID column
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2316?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2316:
-----------------------------------
Fix Version/s: 8.6
> Excel import creates wrong datatype for ROW_ID column
> -----------------------------------------------------
>
> Key: TEIIDDES-2316
> URL: https://issues.jboss.org/browse/TEIIDDES-2316
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Import/Export, Modeling, Teiid Integration
> Affects Versions: 8.6
> Environment: Teiid Designer 8.6.0.Alpha1
> Teiid 8.7.1
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Fix For: 8.6
>
>
> Following https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable (Option 1 using Teiid Designer), the imported model has the ROW_ID column modeled with datatype "integer", which results in BigInteger runtime datatype. After adding this model to a vdb and deploying, the following queries work ok:
> {code:sql}
> SELECT * FROM Sheet1
> SELECT * FROM Sheet1 WHERE row_id > 2
> {code}
> but the following query fails:
> {code:sql}
> SELECT * FROM Sheet1 WHERE row_id = 2
> {code}
> The error is
> bq. org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidException: java.math.BigInteger cannot be cast to java.lang.Integer
> After changing the datatype to "int : xs:long" and redeploying, the above query works as expected.
> However, if I copy the generated dynamic vdb (attached) and deploy it on the server (without using Designer), running the query against that works.
> The DDL for import is
> {code:sql}
> SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel;
> CREATE FOREIGN TABLE Sheet1 (
> ROW_ID integer OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_excel:CELL_NUMBER" 'ROW_ID'),
> FirstName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '1'),
> LastName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '2'),
> Age double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '3'),
> CONSTRAINT PK0 PRIMARY KEY(ROW_ID)
> ) OPTIONS ("teiid_excel:FILE" 'names.xlsx', "teiid_excel:FIRST_DATA_ROW_NUMBER" '2');
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months