[JBoss JIRA] (TEIIDDES-3113) When creating VDB where new infinispan-hotrod translator, missing native metadata tag
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3113?page=com.atlassian.jira.plu... ]
Van Halbert reassigned TEIIDDES-3113:
-------------------------------------
Assignee: Barry LaFond
> When creating VDB where new infinispan-hotrod translator, missing native metadata tag
> -------------------------------------------------------------------------------------
>
> Key: TEIIDDES-3113
> URL: https://issues.jboss.org/browse/TEIIDDES-3113
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 11.1.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
>
> When a VDB is being created that contains a model that uses the new infinispan-hotrod translator, the created VDB is missing the following native tag:
> <metadata type = "NATIVE"/>
> The source model should contain 2 metadata entries, the following is an example:
> {code}
> <model name="People">
> <source connection-jndi-name="java:/infinispanPerson" name="infinispan" translator-name="infinispan-hotrod"/>
> <metadata type = "DDL"><![CDATA[
> CREATE FOREIGN TABLE Person (id integer PRIMARY KEY, name varchar(100), salary double) OPTIONS(UPDATABLE true, "teiid_ispn:cache" 'personCache');
> ]]>
> </metadata>
> <metadata type = "NATIVE"/>
> </model>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (TEIIDDES-3113) When creating VDB where new infinispan-hotrod translator, missing native metadata tag
by Van Halbert (JIRA)
Van Halbert created TEIIDDES-3113:
-------------------------------------
Summary: When creating VDB where new infinispan-hotrod translator, missing native metadata tag
Key: TEIIDDES-3113
URL: https://issues.jboss.org/browse/TEIIDDES-3113
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 11.1.1
Reporter: Van Halbert
Priority: Blocker
When a VDB is being created that contains a model that uses the new infinispan-hotrod translator, the created VDB is missing the following native tag:
<metadata type = "NATIVE"/>
The source model should contain 2 metadata entries, the following is an example:
{code}
<model name="People">
<source connection-jndi-name="java:/infinispanPerson" name="infinispan" translator-name="infinispan-hotrod"/>
<metadata type = "DDL"><![CDATA[
CREATE FOREIGN TABLE Person (id integer PRIMARY KEY, name varchar(100), salary double) OPTIONS(UPDATABLE true, "teiid_ispn:cache" 'personCache');
]]>
</metadata>
<metadata type = "NATIVE"/>
</model>
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (TEIIDDES-3112) Add search capabilities to the VDB Definition screens
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-3112:
--------------------------------------
Summary: Add search capabilities to the VDB Definition screens
Key: TEIIDDES-3112
URL: https://issues.jboss.org/browse/TEIIDDES-3112
Project: Teiid Designer
Issue Type: Feature Request
Components: VDB & Execution
Reporter: Debbie Steigner
Assignee: Barry LaFond
Priority: Critical
Fix For: 11.1.1
Attachments: data-role-editor-filter-options.png, vdb-editor-filter-options.png
To improve JDV Designer productivity, we would like to request an implementation of the following points regarding the VDB configuration panel (see page 2 attachment JDV_RFE_navigation.pdf):
- Full Text Search, enabling to search entities "starts with", "contains", or "end with".
- Filter by Type: ALL, View, VBL, DataSource (select the types of entities i want to search into).
- Clear Search Fields: Clear all of the above.
- Order By Name: ASC, DESC. Order by name all the entities, and make click-able the Name Header bar to change ascending and descending ordering.
The same improvements could be introduced in the Data Roles permissions panes (see page 4 attachment JDV_RFE_navigation.pdf).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (TEIIDDES-3103) Execute VDB in the Guides doesn't work
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3103?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-3103:
----------------------------------------
[~mkralik] I've tested all the ways Designer provides to Deploy VDB and they all work for me. I'm using JDV 6.4 ER2 install. What's your version of JBDS/Eclipse did you install Designer into?
> Execute VDB in the Guides doesn't work
> --------------------------------------
>
> Key: TEIIDDES-3103
> URL: https://issues.jboss.org/browse/TEIIDDES-3103
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1
> Environment: Fedora 26
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 11.1.1
>
> Attachments: guides.mkv, screenshot.png
>
>
> Last step (execute VDB) in the first guide (Model JDBC Source) doesn't work. After click on the "Execute VDB" shows wizard for choosing VDB (screenshot1). After click OK, VDB is not deployed.
> I noticed that it doesn't work in the other guides as well.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[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 commented on TEIIDDES-2874:
----------------------------------------
Took yet another stab at this issue, with no luck. Resizing the dialog window is the only way to display the content of the second view.
> 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: 11.3
>
>
> 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
(v7.2.3#72005)
6 years, 7 months