[JBoss JIRA] (TEIIDDES-3118) Error using option to generate xml from VDB
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3118?page=com.atlassian.jira.plu... ]
Matus Makovy closed TEIIDDES-3118.
----------------------------------
Verified with TD 11.1.1.v20171023-1904.
Closing
> Error using option to generate xml from VDB
> -------------------------------------------
>
> Key: TEIIDDES-3118
> URL: https://issues.jboss.org/browse/TEIIDDES-3118
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 11.1.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 11.1.1
>
> Attachments: designer.log, projectset.zip
>
>
> Using the attached project set. When the view model is included when trying the option: Modeling ==> Generate VDB XML and error is encountered.
> If I remove the view model and save the vdb, then try the generate option, it works.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (TEIIDDES-3101) Import using Teiid Connection does not work
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3101?page=com.atlassian.jira.plu... ]
Matus Makovy commented on TEIIDDES-3101:
----------------------------------------
Verified with TD 11.1.1.v20171023-1904.
Closing
> Import using Teiid Connection does not work
> -------------------------------------------
>
> Key: TEIIDDES-3101
> URL: https://issues.jboss.org/browse/TEIIDDES-3101
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 11.1
> Reporter: Mario Majernik
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 11.1
>
> Attachments: screen1.png, screen2.png, screen3.png
>
>
> Import using teiid connection does not work. When I try import it always ends with timeout fail. (screens 1 +2 + 3 ). I tried at least 10 connections that worked in previous designers.
> Server log says that VDB is ACTIVE:
> 09:50:48,405 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (teiid-async-threads - 2) TEIID40003 VDB importVDB.1 is set to ACTIVE
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (TEIIDDES-3101) Import using Teiid Connection does not work
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3101?page=com.atlassian.jira.plu... ]
Matus Makovy closed TEIIDDES-3101.
----------------------------------
> Import using Teiid Connection does not work
> -------------------------------------------
>
> Key: TEIIDDES-3101
> URL: https://issues.jboss.org/browse/TEIIDDES-3101
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 11.1
> Reporter: Mario Majernik
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 11.1
>
> Attachments: screen1.png, screen2.png, screen3.png
>
>
> Import using teiid connection does not work. When I try import it always ends with timeout fail. (screens 1 +2 + 3 ). I tried at least 10 connections that worked in previous designers.
> Server log says that VDB is ACTIVE:
> 09:50:48,405 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (teiid-async-threads - 2) TEIID40003 VDB importVDB.1 is set to ACTIVE
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (TEIIDDES-2865) JDBC importer imports MSSQL Server datatype numeric(9, [0-9]) as bigdecimal with zero precision
by Debbie Steigner (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2865?page=com.atlassian.jira.plu... ]
Debbie Steigner commented on TEIIDDES-2865:
-------------------------------------------
This issue still exists in 11.1.1, for all Databases not just MSSQL, an Oracle NUMBER(22) for example imports with length of 22 but precision of 0 and should be 22.
Customer ticket - https://access.redhat.com/support/cases/01950882
> JDBC importer imports MSSQL Server datatype numeric(9,[0-9]) as bigdecimal with zero precision
> ----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2865
> URL: https://issues.jboss.org/browse/TEIIDDES-2865
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 10.0, 9.0.5, 9.0.6, 9.0.7
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 11.1, 11.1.1
>
>
> JDBC importer imports MSSQL Server datatype numeric(9,[0-9]) as bigdecimal with zero precision and should be 9. I believe this https://issues.jboss.org/browse/TEIIDDES-2746 may have changed the behavior, in version 9.0.3 it imports correctly.
> You can use jdbc:sqlserver://ENGNTDBS14.mw.lab.eng.bos.redhat.com:1433;databaseName=mss_eds
> user - mss_eds
> password - mss_eds
> table - debtest2, both columns are numeric(9,2)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (TEIIDDES-2865) JDBC importer imports MSSQL Server datatype numeric(9, [0-9]) as bigdecimal with zero precision
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2865?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2865.
------------------------------------
Fix Version/s: 11.1.1
Resolution: Done
master: https://github.com/Teiid-Designer/teiid-designer/commit/69204158ad6efb797...
> JDBC importer imports MSSQL Server datatype numeric(9,[0-9]) as bigdecimal with zero precision
> ----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2865
> URL: https://issues.jboss.org/browse/TEIIDDES-2865
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 10.0, 9.0.5, 9.0.6, 9.0.7
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 11.1.1, 11.1
>
>
> JDBC importer imports MSSQL Server datatype numeric(9,[0-9]) as bigdecimal with zero precision and should be 9. I believe this https://issues.jboss.org/browse/TEIIDDES-2746 may have changed the behavior, in version 9.0.3 it imports correctly.
> You can use jdbc:sqlserver://ENGNTDBS14.mw.lab.eng.bos.redhat.com:1433;databaseName=mss_eds
> user - mss_eds
> password - mss_eds
> table - debtest2, both columns are numeric(9,2)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[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 updated TEIIDDES-2493:
-----------------------------------
Fix Version/s: 11.1.1
> 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: Barry LaFond
> Fix For: 11.1, 11.1.1
>
> Attachments: screenshot.png
>
>
> 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
(v7.5.0#75005)
8 years, 5 months