[JBoss JIRA] (TEIIDDES-2847) Flat File Importer doesn't accept multi-character delimiter
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2847?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2847:
-----------------------------------
Fix Version/s: (was: 10.1)
> Flat File Importer doesn't accept multi-character delimiter
> -----------------------------------------------------------
>
> Key: TEIIDDES-2847
> URL: https://issues.jboss.org/browse/TEIIDDES-2847
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.6
> Environment: Red Hat JBoss Data Virtualization 6.2.4 on EAP patched to version 6.4.6, on Oracle Linux 6
> JBoss Developer Studio 8.1.0GA with Teiid Designer 9.0.6.Final-v20160316-1409-B1242 org.teiid.designer.feature.feature.group JBoss by Red Hat, Inc.
> 64-bit Windows 7 environment
> Reporter: Steve Tran
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 10.0.1, 10.0.2
>
> Attachments: productdata_data.csv, Screenshot.png, screenshot2.png
>
>
> I tried importing a file, but needed to specify a multi-character delimiter. The box lets me enter it, but only the first character is actually used. When I open the window that asked me for the delimiter again, only the first character is showing. There are situations when the delimiter is multi-character, so restricting input on the text box to one-character shouldn't be the solution.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2858) Column whose have specific name in not correctly parsed in the DDL
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2858?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2858:
-----------------------------------
Fix Version/s: (was: 10.1)
> Column whose have specific name in not correctly parsed in the DDL
> ------------------------------------------------------------------
>
> Key: TEIIDDES-2858
> URL: https://issues.jboss.org/browse/TEIIDDES-2858
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview, Dynamic VDBs
> Affects Versions: 10.0.1
> Environment: Fedora 23
> Reporter: Matej Kralik
> Fix For: 10.0.2
>
> Attachments: remoteXML.zip, screenshot1.png, screenshot2.png
>
>
> When I wanted preview date from the table which contains column with specific name, server shows me this error:
> TEIID31100 Parsing error: Encountered "'FALSE'), [*]YEAR[*] string(" at line 8, column 9.
> Was expecting: "constraint" | "foreign" | "primary" | "unique" | id
> I looked on the DDL which designer generated (screenshot1) and I think that column TIME should be between quotation marks.
> "YEAR" string(4000) OPTIONS(NAMEINSOURCE '"YEAR"', UPDATABLE 'FALSE')
> When I change column name from TIME to "TIME", the preview passed and showed me data. (screenshot2)
> A similar situation is when I generated dynamic VDB.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2831) Vdb conversion should exclude model 'checksum' and 'index' properties
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2831?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-2831:
-----------------------------------
Labels: release_notes verified_jbdsis-9.0.1 (was: )
> Vdb conversion should exclude model 'checksum' and 'index' properties
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-2831
> URL: https://issues.jboss.org/browse/TEIIDDES-2831
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 10.0
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Labels: release_notes, verified_jbdsis-9.0.1
> Fix For: 10.0.1
>
>
> Conversion of an xmi vdb to a dynamic vdb simply copies all properties contained in models. However, this includes both the 'checksum' and 'indexName' properties which are not applicable to dynamic vdbs. Worse still this is counter-productive since the Dynamic Vdb Sequencers in Komodo actually use the 'indexName' property to determine if the model is Declarative or not, excluding those models with the property present.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2831) Vdb conversion should exclude model 'checksum' and 'index' properties
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2831?page=com.atlassian.jira.plu... ]
Matus Makovy closed TEIIDDES-2831.
----------------------------------
> Vdb conversion should exclude model 'checksum' and 'index' properties
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-2831
> URL: https://issues.jboss.org/browse/TEIIDDES-2831
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 10.0
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Labels: release_notes, verified_jbdsis-9.0.1
> Fix For: 10.0.1
>
>
> Conversion of an xmi vdb to a dynamic vdb simply copies all properties contained in models. However, this includes both the 'checksum' and 'indexName' properties which are not applicable to dynamic vdbs. Worse still this is counter-productive since the Dynamic Vdb Sequencers in Komodo actually use the 'indexName' property to determine if the model is Declarative or not, excluding those models with the property present.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months