October 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2558) Add translator support for dependent join pushdown

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2558?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2558. --------------------------------- > Add translator support for dependent join pushdown > -------------------------------------------------- > > Key: TEIID-2558 > URL: https://issues.jboss.org/browse/TEIID-2558 > Project: Teiid > Issue Type: Sub-task > Components: Connector API > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.5 > > > JDBC translators should offer built-in support for dependent join pushdown - possibly with index creation and other options. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3033. --------------------------------- > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3068) Each vdb should be protected by its own security-domain

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3068?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3068. --------------------------------- > Each vdb should be protected by its own security-domain > -------------------------------------------------------- > > Key: TEIID-3068 > URL: https://issues.jboss.org/browse/TEIID-3068 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.4.1 > Reporter: Hisanobu Okuda > Assignee: Steven Hawkins > > Every vdbs are protected by single security-realm. It does not fit some enterprise requirement on a security workflow. Ideally, each vdb should be protected by its own security-domain like a servlet and an EJB. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3158) VDB versioning does not work

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3158?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3158. --------------------------------- > VDB versioning does not work > ---------------------------- > > Key: TEIID-3158 > URL: https://issues.jboss.org/browse/TEIID-3158 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4.1 > Environment: - JDV 6.0.0 > Reporter: Hisanobu Okuda > Assignee: Steven Hawkins > > The vdb "test.1.vdb" should be deployed as the vdb "test" of the version "1" as described in [1]. But, it is deployed as the vdb "test.1" in fact as following:- > {code} > 20:48:20,210 INFO [org.jboss.as.repository] (management-handler-thread - 6) JBAS014900: Content added at location /opt/dv600/jboss-eap-6.1/standalone/data/content/b8/a0bf2213af6edc2817c63f149f760d1d796cda/content > 20:48:20,212 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "test.1.vdb" (runtime-name: "test.1.vdb") > 20:48:20,270 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB test.1 model "SourceModel" metadata is currently being loaded. Start Time: 10/2/14 8:48 PM > 20:48:20,273 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB test.1 model "ViewModel" metadata is currently being loaded. Start Time: 10/2/14 8:48 PM > 20:48:20,296 INFO [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50030 VDB test.1 model "ViewModel" metadata loaded. End Time: 10/2/14 8:48 PM > 20:48:20,296 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50030 VDB test.1 model "SourceModel" metadata loaded. End Time: 10/2/14 8:48 PM > 20:48:20,300 INFO [org.jboss.as.server] (management-handler-thread - 6) JBAS018559: Deployed "test.1.vdb" (runtime-name : "test.1.vdb") > 20:48:20,334 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) Data Source SourceModel not accessible. > 20:48:20,334 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID40003 VDB test.1 is set to ACTIVE > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3091) Excel translator issue: FIRST_DATA_ROW_NUMBER option not working

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3091?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3091. --------------------------------- > Excel translator issue: FIRST_DATA_ROW_NUMBER option not working > ----------------------------------------------------------------- > > Key: TEIID-3091 > URL: https://issues.jboss.org/browse/TEIID-3091 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Attachments: excel.png, excel_row_number_issue.tiff, otherholdings.xls, portfolio-vdb.xml > > > The FIRST_DATA_ROW_NUMBER option not working, seeing the first row in the results, when using the following dynamic VDB definition: > {code} > <model name="OtherHoldings"> > <property name="importer.headerRowNumber" value="1"/> > <property name="importer.ExcelFileName" value="otherholdings.xls"/> > <source name="excelconnector" translator-name="excel" connection-jndi-name="java:/excel-file"/> > <metadata type="DDL"><![CDATA[ > SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel; > CREATE FOREIGN TABLE Sheet1 ( > ROW_ID integer OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_excel:CELL_NUMBER" 'ROW_ID'), > FirstName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '1'), > LastName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '2'), > Age string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '3'), > CONSTRAINT PK0 PRIMARY KEY(ROW_ID) > ) OPTIONS ("teiid_excel:FILE" 'otherholdings.xls', "teiid_excel:FIRST_DATA_ROW_NUMBER" '2'); > ]]> </metadata> > </model> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2817) XML Modeling Lab 7 and runtime errors on DV 6.0 Beta

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2817?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2817. --------------------------------- > XML Modeling Lab 7 and runtime errors on DV 6.0 Beta > ---------------------------------------------------- > > Key: TEIID-2817 > URL: https://issues.jboss.org/browse/TEIID-2817 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Gary Lamperillo > Assignee: Steven Hawkins > Fix For: 8.7 > > Attachments: Financial_VDB.vdb > > > The XML schema is imported and the modeling is completed per the Lab on XML modeling. At runtime, during VDB execution, the sql scrap pad has the sql entered - select * from CustomerHoldingsXML.CustomersDocument > At this point the following error is displayed: > TEIID30328 Unable to evaluate "INPUT".AccountID: No value was available > The VDB will be attached per Steven Hawkins request. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2424) Create OSGi bundles for Embedded

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2424?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2424. --------------------------------- > Create OSGi bundles for Embedded > -------------------------------- > > Key: TEIID-2424 > URL: https://issues.jboss.org/browse/TEIID-2424 > Project: Teiid > Issue Type: Feature Request > Components: AdminApi, Embedded > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.6 > > > Embedded should be available as an OSGi bundle(s). It may also be useful for Designer to consume us through bundles as well. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2978) using LIKE on columns causes no results though they indeed exist

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2978?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2978. --------------------------------- > using LIKE on columns causes no results though they indeed exist > ---------------------------------------------------------------- > > Key: TEIID-2978 > URL: https://issues.jboss.org/browse/TEIID-2978 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Tom Johnston > Assignee: Van Halbert > Labels: modeshape, teiid > > Use of LIKE doesn't appear to work when querying modeshape through JDBC. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2835) After switch to use io.netty, getting exception in TestJDBCSocketTransport

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2835?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2835. --------------------------------- > After switch to use io.netty, getting exception in TestJDBCSocketTransport > -------------------------------------------------------------------------- > > Key: TEIID-2835 > URL: https://issues.jboss.org/browse/TEIID-2835 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7 > Environment: Running build on mac > Reporter: Van Halbert > Assignee: Steven Hawkins > > When building off of master (which I see there's been a change to io.netty), I get the following error: > Running org.teiid.transport.TestJDBCSocketTransport > Feb 3, 2014 2:51:12 PM org.teiid.logging.JavaLogger log > SEVERE: TEIID40113 Unhandled exception, aborting operation > org.jboss.netty.handler.codec.frame.TooLongFrameException: Adjusted frame length exceeds 100000: 100293 - discarded > at org.jboss.netty.handler.codec.frame.LengthFieldBasedFrameDecoder.fail(LengthFieldBasedFrameDecoder.java:417) > at org.jboss.netty.handler.codec.frame.LengthFieldBasedFrameDecoder.failIfNecessary(LengthFieldBasedFrameDecoder.java:405) > at org.jboss.netty.handler.codec.frame.LengthFieldBasedFrameDecoder.decode(LengthFieldBasedFrameDecoder.java:320) > at org.teiid.transport.ObjectDecoder.decode(ObjectDecoder.java:108) > at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425) > at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) > at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) > at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107) > at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) > at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88) > at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:695) > I made a change to SSLAwareChannelHandler to increase the estimated decoder size to Integer.MAX_VALUE and the problem was gone. Here's the difference in size estimates based on what the default was using and the MAX_VALUE I tested with: > =========== DEFAULT ===========2097152 > =========== Int Max ===========2147483647 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2789) Create maven archtype for connector development

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2789?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2789. --------------------------------- > Create maven archtype for connector development > ----------------------------------------------- > > Key: TEIID-2789 > URL: https://issues.jboss.org/browse/TEIID-2789 > Project: Teiid > Issue Type: Feature Request > Components: Tools > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Optional > Fix For: 8.6 > > > Create a maven archtype project for creating the archetype that can be used for connector development -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2014