[JBoss JIRA] (TEIIDDES-2109) Create a Connections context menu group next to Modeling group
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2109?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2109.
------------------------------------
Resolution: Won't Do
> Create a Connections context menu group next to Modeling group
> --------------------------------------------------------------
>
> Key: TEIIDDES-2109
> URL: https://issues.jboss.org/browse/TEIIDDES-2109
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling, Views
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 9.2.1
>
> Attachments: connection-action-menu.png
>
>
> For source models, the Modeling action now contains a number of connection or translator related actions that really don't have anything to do with modeling.
> * Create a *Connection* menu group and place below *Modeling* group
> * Move the following actions to the *Connection* group
> ** Create Data Source
> ** Edit Translator Overrides
> ** Remove Connection Info
> ** Set Connection Profile
> ** Set Translator Name
> ** View Connection Profile Info
> * Maybe group these into Translator/Profile actions with separators
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2152) Adding source table with quoted name results in wrong generated SQL statement
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2152?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2152:
-----------------------------------
Component/s: Patch Release
> Adding source table with quoted name results in wrong generated SQL statement
> -----------------------------------------------------------------------------
>
> Key: TEIIDDES-2152
> URL: https://issues.jboss.org/browse/TEIIDDES-2152
> Project: Teiid Designer
> Issue Type: Bug
> Components: Patch Release, Transformations
> Affects Versions: 8.5
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 9.2.1
>
>
> 1) Created source model with simple table named "My.Quoted.Table" (including quotes
> 2) Created simple virtual table and pasted: SELECT * FROM "My.Quoted.Table"
> 3) Parser returned a command resulting in the SQL: SELECT * FROM My.Quoted."Table"
> Parser should be able to handle quoted names properly. In this case the SQL should have been valid as is.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2217) TEIID30183 Message:TEIID30183 Text parse error: Non-whitespace character found between the qualifier and the delimiter in text line 16, 161 in Unknown. SQLState: TEIID30183
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2217?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2217.
------------------------------------
Resolution: Out of Date
> TEIID30183 Message:TEIID30183 Text parse error: Non-whitespace character found between the qualifier and the delimiter in text line 16,161 in Unknown. SQLState: TEIID30183
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2217
> URL: https://issues.jboss.org/browse/TEIIDDES-2217
> Project: Teiid Designer
> Issue Type: Quality Risk
> Reporter: luca gioppo
> Priority: Minor
> Fix For: 9.2.1
>
>
> On the same use case of TEIID30181 I now got the error in object:
> TEIID30183 Message:TEIID30183 Text parse error: Non-whitespace character found between the qualifier and the delimiter in text line 16,161 in Unknown.
> SQLState: TEIID30183
> the row should be:
> istsc_pgee021002 Direzione Didattica Statale "Franco Rasetti" Castiglione del Lago ANTONIETTA MANNUCCI 06061 PG Umbria www.dirclago.it Via Carducci, 25 Dirigente Scolastico Istituti di Istruzione Statale di Ogni Ordine e Grado Pubbliche Amministrazioni S 80005650546 pgee021002(a)pec.istruzione.it pec pgee021002(a)istruzione.it altro null null null null null null 0
> the only difference I find between the previous rows that passed without problems is that a field has double quote in its content.
> The delimiter is tabulation so there should not be any problem.
> Could it be this the problem and how to solve it?
> Thanks
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2219) Preview Issue - when non-Type4 JDBC driver is used.
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2219?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2219:
-----------------------------------
Fix Version/s: 10.1
(was: 9.2.1)
> Preview Issue - when non-Type4 JDBC driver is used.
> ---------------------------------------------------
>
> Key: TEIIDDES-2219
> URL: https://issues.jboss.org/browse/TEIIDDES-2219
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview, Patch Release
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 10.1
>
> Attachments: ojdbc14.jar
>
>
> Encountered issue when trying to preview an Oracle source table in Designer. The preview failed with the following in the server log:
> 10:39:44,877 WARN [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue0) TEIID30020 Processing exception for request N0JYBgYp8yw2.0 'TEIID30498 Capabilities for OracleSource were not avaialable. The command could not be planned properly.'. Originally QueryPlannerException PlanToProcessConverter.java:324. Enable more detailed logging to see the entire stacktrace.
> Upon debug, I found that the 'type' for my deployed oracle driver 'ojdbc14.jar' was not found on the server. The ojdbc14.jar was actually getting deployed in ExecutionAdmin, but the type was not present - because it was not a type4 jdbc driver.
> However, the preview proceeded (and failed) with the above exception.
> We need to investigate and handle this case more gracefully in Designer. The preview should not proceed - we should catch this error and display to the user - and stop the preview attempt.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2219) Preview Issue - when non-Type4 JDBC driver is used.
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2219?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2219:
-----------------------------------
Component/s: Patch Release
> Preview Issue - when non-Type4 JDBC driver is used.
> ---------------------------------------------------
>
> Key: TEIIDDES-2219
> URL: https://issues.jboss.org/browse/TEIIDDES-2219
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview, Patch Release
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 9.2.1
>
> Attachments: ojdbc14.jar
>
>
> Encountered issue when trying to preview an Oracle source table in Designer. The preview failed with the following in the server log:
> 10:39:44,877 WARN [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue0) TEIID30020 Processing exception for request N0JYBgYp8yw2.0 'TEIID30498 Capabilities for OracleSource were not avaialable. The command could not be planned properly.'. Originally QueryPlannerException PlanToProcessConverter.java:324. Enable more detailed logging to see the entire stacktrace.
> Upon debug, I found that the 'type' for my deployed oracle driver 'ojdbc14.jar' was not found on the server. The ojdbc14.jar was actually getting deployed in ExecutionAdmin, but the type was not present - because it was not a type4 jdbc driver.
> However, the preview proceeded (and failed) with the above exception.
> We need to investigate and handle this case more gracefully in Designer. The preview should not proceed - we should catch this error and display to the user - and stop the preview attempt.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2265) Allow MultiSelect Columns for creation of indexes
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2265?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2265:
-----------------------------------
Fix Version/s: 10.1
(was: 9.2.1)
> Allow MultiSelect Columns for creation of indexes
> -------------------------------------------------
>
> Key: TEIIDDES-2265
> URL: https://issues.jboss.org/browse/TEIIDDES-2265
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling
> Reporter: Tom Johnston
> Assignee: Barry LaFond
> Fix For: 10.1
>
>
> I just realized a pain point.
> I have a need to create a number of indexes on views (as they are going to be materialized) but there seems no easy way but one by one.
> I envision the following:
> Multi-select columns (in Model explorer OR Table editor ) and click Modeling and choose Create index (also UK and PK I would think) .. suggest a 'template' (i.e. tableName_ColumnName_IX (auto add 1...x if something or more than one exists) If I choose 2 cols from one table then a check to create one or multiple (default to multiple)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months