[JBoss JIRA] (TEIIDDES-2874) Oracle Views import with no columns via "JDBC Importer"
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2874?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2874:
--------------------------------------
Assignee: Barry LaFond
> Oracle Views import with no columns via "JDBC Importer"
> -------------------------------------------------------
>
> Key: TEIIDDES-2874
> URL: https://issues.jboss.org/browse/TEIIDDES-2874
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.3, 10.0, 9.0.7
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 10.0.2
>
>
> Tested in Teiid Designer 9.0.3, 9.0.7 and 10
> I see the same behavior, using bqt2 on jdbc:oracle:thin:@englxdbs11.mw.lab.eng.bos.redhat.com:1521:orcl there are 2 views, v1234 and smalla_view, if you import both of them only the smalla_view is complete, the v1234 creates the table with no columns.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIIDDES-2884) User can create empty Unique Constraint
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2884?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2884:
--------------------------------------
Assignee: Barry LaFond
> User can create empty Unique Constraint
> ---------------------------------------
>
> Key: TEIIDDES-2884
> URL: https://issues.jboss.org/browse/TEIIDDES-2884
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.1
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
> Attachments: Screen Shot 2016-07-27 at 12.46.33.png, Screen Shot 2016-07-27 at 12.46.41.png, Screen Shot 2016-07-27 at 12.46.48.png
>
>
> You can create unique constraint on table without giving it a name or column reference.
> There is no error when you open the dialogue and OK is enabled.
> See screenshots
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIIDDES-2887) Unable to edit the admin port on the Teiid Instance Tab
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2887?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2887:
-----------------------------------
Fix Version/s: 10.0.2
> Unable to edit the admin port on the Teiid Instance Tab
> -------------------------------------------------------
>
> Key: TEIIDDES-2887
> URL: https://issues.jboss.org/browse/TEIIDDES-2887
> Project: Teiid Designer
> Issue Type: Bug
> Components: Usability
> Affects Versions: 10.0.2
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 10.0.2
>
>
> When the DV server is started with port offsets means that in Teiid Designer, the Teiid Instance tab, the admin port needs to be adjusted accordingly. However, its not editable and doesn't pull its info from the Overview tab when port offsets are configured. This issue arises in cases where the server is externally administered and you don't wan to have to install a local EAP instance in order to manage it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIIDDES-2887) Unable to edit the admin port on the Teiid Instance Tab
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2887?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2887:
--------------------------------------
Assignee: Barry LaFond
> Unable to edit the admin port on the Teiid Instance Tab
> -------------------------------------------------------
>
> Key: TEIIDDES-2887
> URL: https://issues.jboss.org/browse/TEIIDDES-2887
> Project: Teiid Designer
> Issue Type: Bug
> Components: Usability
> Affects Versions: 10.0.2
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 10.0.2
>
>
> When the DV server is started with port offsets means that in Teiid Designer, the Teiid Instance tab, the admin port needs to be adjusted accordingly. However, its not editable and doesn't pull its info from the Overview tab when port offsets are configured. This issue arises in cases where the server is externally administered and you don't wan to have to install a local EAP instance in order to manage it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIIDDES-2888) Default value is not correctly parsed
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2888?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2888:
----------------------------------------
[~mkralik] If preview is not working, then it's a matter of the DDL builder in Designer that converts EMF to DDL for the column and it's default value. So would be a matter of converting a valid value that can be parsed by Teiid. Can you provide a valid default value string I can use thats valid? i.e. hand-edit a dynamic VDB and deploy it to verify parsing works? thx
> Default value is not correctly parsed
> --------------------------------------
>
> Key: TEIIDDES-2888
> URL: https://issues.jboss.org/browse/TEIIDDES-2888
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview, Dynamic VDBs
> Affects Versions: 10.0.1
> Environment: Fedora 24
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
> Attachments: ProductProject.zip, screenshot1.png, screenshot2.png
>
>
> When I want preview data from my table (productdata in the project which is in the attachment), server shows me this error:
> TEIID31100 Parsing error: Encountered ") DEFAULT '('[*]Stock[*]')' OPTIONS"
> In one column I have default value ('Stock') (screenshot1)
> I am not sure whether it is the correct form of default value or not but in the old version of teiid designer preview this table works fine. I think that ddl parser is not able to parse this. (screenshot2)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIIDDES-2888) Default value is not correctly parsed
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2888?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2888:
-----------------------------------
Fix Version/s: 10.0.2
> Default value is not correctly parsed
> --------------------------------------
>
> Key: TEIIDDES-2888
> URL: https://issues.jboss.org/browse/TEIIDDES-2888
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview, Dynamic VDBs
> Affects Versions: 10.0.1
> Environment: Fedora 24
> Reporter: Matej Kralik
> Fix For: 10.0.2
>
> Attachments: ProductProject.zip, screenshot1.png, screenshot2.png
>
>
> When I want preview data from my table (productdata in the project which is in the attachment), server shows me this error:
> TEIID31100 Parsing error: Encountered ") DEFAULT '('[*]Stock[*]')' OPTIONS"
> In one column I have default value ('Stock') (screenshot1)
> I am not sure whether it is the correct form of default value or not but in the old version of teiid designer preview this table works fine. I think that ddl parser is not able to parse this. (screenshot2)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIIDDES-2888) Default value is not correctly parsed
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2888?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2888:
--------------------------------------
Assignee: Barry LaFond
> Default value is not correctly parsed
> --------------------------------------
>
> Key: TEIIDDES-2888
> URL: https://issues.jboss.org/browse/TEIIDDES-2888
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview, Dynamic VDBs
> Affects Versions: 10.0.1
> Environment: Fedora 24
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
> Attachments: ProductProject.zip, screenshot1.png, screenshot2.png
>
>
> When I want preview data from my table (productdata in the project which is in the attachment), server shows me this error:
> TEIID31100 Parsing error: Encountered ") DEFAULT '('[*]Stock[*]')' OPTIONS"
> In one column I have default value ('Stock') (screenshot1)
> I am not sure whether it is the correct form of default value or not but in the old version of teiid designer preview this table works fine. I think that ddl parser is not able to parse this. (screenshot2)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIIDDES-2895) No warning after deleting schema and UDF Jars
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2895?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2895:
-----------------------------------
Fix Version/s: 10.0.2
> No warning after deleting schema and UDF Jars
> ---------------------------------------------
>
> Key: TEIIDDES-2895
> URL: https://issues.jboss.org/browse/TEIIDDES-2895
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Affects Versions: 10.0.1
> Reporter: Mario Majernik
> Fix For: 10.0.2
>
> Attachments: ScreenShot1.png, XmlStagingTableProject.zip
>
>
> There is no warning after deleting schema which is used by models. VDB is deployed without warnings. Following query fails on missing schema.
> Should be there some warning that schema was deleted and VDB should not be deploy on server without schema.
> EDIT: The same thing with UDF Jars. No warning after deleting but VDB is corrupt after deploying on server.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIIDDES-2895) No warning after deleting schema and UDF Jars
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2895?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2895:
--------------------------------------
Assignee: Barry LaFond
> No warning after deleting schema and UDF Jars
> ---------------------------------------------
>
> Key: TEIIDDES-2895
> URL: https://issues.jboss.org/browse/TEIIDDES-2895
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Affects Versions: 10.0.1
> Reporter: Mario Majernik
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
> Attachments: ScreenShot1.png, XmlStagingTableProject.zip
>
>
> There is no warning after deleting schema which is used by models. VDB is deployed without warnings. Following query fails on missing schema.
> Should be there some warning that schema was deleted and VDB should not be deploy on server without schema.
> EDIT: The same thing with UDF Jars. No warning after deleting but VDB is corrupt after deploying on server.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months