June 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4164) Correct the transitive dependencies in OData4 translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4164?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4164: -------------------------------- Fix Version/s: 9.0 > Correct the transitive dependencies in OData4 translator > -------------------------------------------------------- > > Key: TEIID-4164 > URL: https://issues.jboss.org/browse/TEIID-4164 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Affects Versions: 9.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Minor > Fix For: 9.0 > > > Currently "com.fasterxml" transitive dependencies are not in "kits" or pom.xml > They need to be explicitly defined as dependencies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4220) Unsupported encoding when POSTing to odata on Windows

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4220?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4220. --------------------------------- Resolution: Done Labels: CR2 (was: ) Corrected the dependencies, it still does not remove the dependency on woodstax. However some dependencies like antlr are no longer needed. > Unsupported encoding when POSTing to odata on Windows > ----------------------------------------------------- > > Key: TEIID-4220 > URL: https://issues.jboss.org/browse/TEIID-4220 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.x > Reporter: Andrej Šmigala > Assignee: Ramesh Reddy > Priority: Critical > Labels: CR2 > Fix For: 9.0 > > > When posting to a windows server from a windows client, the default encoding is cp1252. When an xml request such as this is posted: > {code:xml} > <?xml version='1.0' encoding='cp1252'?><entry xmlns="http://www.w3.org/2005/Atom" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:m="http://docs.oasis-open.org/odata/ns/metadata" xmlns:d="http://docs.oasis-open.org/odata/ns/data" xmlns:gml="http://www.opengis.net/gml" xmlns:georss="http://www.georss.org/georss"><category scheme="http://docs.oasis-open.org/odata/ns/scheme"/> > <content type="application/xml"> > <m:properties> > <d:intkey m:type="Int32">4</d:intkey> > <d:intnum m:type="Int32">4</d:intnum> > <d:stringkey>4</d:stringkey> > <d:stringval>value_4</d:stringval> > <d:booleanval m:type="Boolean">false</d:booleanval> > <d:decimalval m:type="Double">-20.4</d:decimalval> > <d:timeval m:type="TimeOfDay">00:00:04</d:timeval> > <d:dateval m:type="Date">2004-04-04</d:dateval> > <d:timestampval m:type="DateTimeOffset">2004-01-01T00:00:04Z</d:timestampval> > </m:properties> > </content> > </entry> > {code} > the following error is logged in the server: > {noformat} > 09:54:38,069 WARN [org.teiid.ODATA] (http-/0.0.0.0:8080-1) TEIID16050 Unable to process odata request due to: An I/O exception occurred. with cause Unsupported encoding: IBM1252: Unsupported encoding: IBM1252 > at org.apache.olingo.server.core.deserializer.xml.ODataXmlDeserializer.entity(ODataXmlDeserializer.java:592) > at org.apache.olingo.server.core.requests.DataRequest$EntityRequest.getEntityFromClient(DataRequest.java:367) > at org.apache.olingo.server.core.requests.DataRequest$EntityRequest.execute(DataRequest.java:359) > at org.apache.olingo.server.core.requests.DataRequest.execute(DataRequest.java:255) > at org.apache.olingo.server.core.ServiceDispatcher.internalExecute(ServiceDispatcher.java:160) > at org.apache.olingo.server.core.ServiceDispatcher.execute(ServiceDispatcher.java:98) > at org.apache.olingo.server.core.OData4HttpHandler.process(OData4HttpHandler.java:66) > at org.teiid.olingo.web.ODataServlet.service(ODataServlet.java:43) [teiid-olingo-8.12.5.redhat-4.jar:8.12.5.redhat-4] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.teiid.olingo.web.ODataFilter.internalDoFilter(ODataFilter.java:226) [teiid-olingo-8.12.5.redhat-4.jar:8.12.5.redhat-4] > at org.teiid.olingo.web.ODataFilter.doFilter(ODataFilter.java:100) [teiid-olingo-8.12.5.redhat-4.jar:8.12.5.redhat-4] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.4.Final-redhat-4.jar:7.5.4.Final-redhat-4] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_79] > Caused by: com.ctc.wstx.exc.WstxIOException: Unsupported encoding: IBM1252 > at com.ctc.wstx.io.StreamBootstrapper.bootstrapInput(StreamBootstrapper.java:247) > at com.ctc.wstx.stax.WstxInputFactory.doCreateSR(WstxInputFactory.java:546) > at com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:600) > at com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:615) > at com.ctc.wstx.stax.WstxInputFactory.createXMLEventReader(WstxInputFactory.java:269) > at __redirected.__XMLInputFactory.createXMLEventReader(__XMLInputFactory.java:170) [jboss-modules.jar:1.3.7.Final-redhat-1] > at org.apache.olingo.server.core.deserializer.xml.ODataXmlDeserializer.getReader(ODataXmlDeserializer.java:97) > at org.apache.olingo.server.core.deserializer.xml.ODataXmlDeserializer.entity(ODataXmlDeserializer.java:583) > ... 26 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4220) Unsupported encoding when POSTing to odata on Windows

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4220?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4220: -------------------------------- Fix Version/s: 9.0 > Unsupported encoding when POSTing to odata on Windows > ----------------------------------------------------- > > Key: TEIID-4220 > URL: https://issues.jboss.org/browse/TEIID-4220 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.x > Reporter: Andrej Šmigala > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 9.0 > > > When posting to a windows server from a windows client, the default encoding is cp1252. When an xml request such as this is posted: > {code:xml} > <?xml version='1.0' encoding='cp1252'?><entry xmlns="http://www.w3.org/2005/Atom" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:m="http://docs.oasis-open.org/odata/ns/metadata" xmlns:d="http://docs.oasis-open.org/odata/ns/data" xmlns:gml="http://www.opengis.net/gml" xmlns:georss="http://www.georss.org/georss"><category scheme="http://docs.oasis-open.org/odata/ns/scheme"/> > <content type="application/xml"> > <m:properties> > <d:intkey m:type="Int32">4</d:intkey> > <d:intnum m:type="Int32">4</d:intnum> > <d:stringkey>4</d:stringkey> > <d:stringval>value_4</d:stringval> > <d:booleanval m:type="Boolean">false</d:booleanval> > <d:decimalval m:type="Double">-20.4</d:decimalval> > <d:timeval m:type="TimeOfDay">00:00:04</d:timeval> > <d:dateval m:type="Date">2004-04-04</d:dateval> > <d:timestampval m:type="DateTimeOffset">2004-01-01T00:00:04Z</d:timestampval> > </m:properties> > </content> > </entry> > {code} > the following error is logged in the server: > {noformat} > 09:54:38,069 WARN [org.teiid.ODATA] (http-/0.0.0.0:8080-1) TEIID16050 Unable to process odata request due to: An I/O exception occurred. with cause Unsupported encoding: IBM1252: Unsupported encoding: IBM1252 > at org.apache.olingo.server.core.deserializer.xml.ODataXmlDeserializer.entity(ODataXmlDeserializer.java:592) > at org.apache.olingo.server.core.requests.DataRequest$EntityRequest.getEntityFromClient(DataRequest.java:367) > at org.apache.olingo.server.core.requests.DataRequest$EntityRequest.execute(DataRequest.java:359) > at org.apache.olingo.server.core.requests.DataRequest.execute(DataRequest.java:255) > at org.apache.olingo.server.core.ServiceDispatcher.internalExecute(ServiceDispatcher.java:160) > at org.apache.olingo.server.core.ServiceDispatcher.execute(ServiceDispatcher.java:98) > at org.apache.olingo.server.core.OData4HttpHandler.process(OData4HttpHandler.java:66) > at org.teiid.olingo.web.ODataServlet.service(ODataServlet.java:43) [teiid-olingo-8.12.5.redhat-4.jar:8.12.5.redhat-4] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.teiid.olingo.web.ODataFilter.internalDoFilter(ODataFilter.java:226) [teiid-olingo-8.12.5.redhat-4.jar:8.12.5.redhat-4] > at org.teiid.olingo.web.ODataFilter.doFilter(ODataFilter.java:100) [teiid-olingo-8.12.5.redhat-4.jar:8.12.5.redhat-4] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.4.Final-redhat-4.jar:7.5.4.Final-redhat-4] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1] > at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_79] > Caused by: com.ctc.wstx.exc.WstxIOException: Unsupported encoding: IBM1252 > at com.ctc.wstx.io.StreamBootstrapper.bootstrapInput(StreamBootstrapper.java:247) > at com.ctc.wstx.stax.WstxInputFactory.doCreateSR(WstxInputFactory.java:546) > at com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:600) > at com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:615) > at com.ctc.wstx.stax.WstxInputFactory.createXMLEventReader(WstxInputFactory.java:269) > at __redirected.__XMLInputFactory.createXMLEventReader(__XMLInputFactory.java:170) [jboss-modules.jar:1.3.7.Final-redhat-1] > at org.apache.olingo.server.core.deserializer.xml.ODataXmlDeserializer.getReader(ODataXmlDeserializer.java:97) > at org.apache.olingo.server.core.deserializer.xml.ODataXmlDeserializer.entity(ODataXmlDeserializer.java:583) > ... 26 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3329) Rationalize older spatial support with the new

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3329?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3329: ---------------------------------- Fix Version/s: 9.1 (was: 9.0) > Rationalize older spatial support with the new > ---------------------------------------------- > > Key: TEIID-3329 > URL: https://issues.jboss.org/browse/TEIID-3329 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Steven Hawkins > Fix For: 9.1 > > > MongoDB and Oracle had existing spatial support that should be updated to account for the new support if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3347) Most subplans do not show node stats

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3347?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3347: ---------------------------------- Fix Version/s: 9.1 (was: 9.0) > Most subplans do not show node stats > ------------------------------------ > > Key: TEIID-3347 > URL: https://issues.jboss.org/browse/TEIID-3347 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > When looking at the node stats, only the direct nodes of the current plan have stats. Subqueries, which are executed off of a cloned plan, do not have stats. > There isn't an easy solution for this with the current design. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3529) Add pushdown support for regexp_replace

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3529?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3529: ---------------------------------- Fix Version/s: 9.1 (was: 9.0) > Add pushdown support for regexp_replace > --------------------------------------- > > Key: TEIID-3529 > URL: https://issues.jboss.org/browse/TEIID-3529 > Project: Teiid > Issue Type: Sub-task > Components: Misc. Connectors, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > At least for sources with similar regex and flags support, we should offer pushdown support. This may require additional support methods to determine if the pattern is acceptable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4030) Improve Geometry Type Handling in HANA Translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4030?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4030: ---------------------------------- Fix Version/s: 9.1 (was: 9.0) > Improve Geometry Type Handling in HANA Translator > ------------------------------------------------- > > Key: TEIID-4030 > URL: https://issues.jboss.org/browse/TEIID-4030 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.13.1 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 9.1 > > > The Geometry type logic in the HANA translator should use the new Teiid Geometry type, similar to the postgres translator. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4094) Move the packaging of teiid-jdbc.jar into is own project

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4094?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4094: --------------------------------------- No, that was just an example. You get a clean dependency with the 8.12.0.Final or 8.11.0.Final versions as well. I think what you were seeing here was an issue introduced by build changes for the product. > Move the packaging of teiid-jdbc.jar into is own project > -------------------------------------------------------- > > Key: TEIID-4094 > URL: https://issues.jboss.org/browse/TEIID-4094 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.5 > > > The issue with the way the teiid-jdbc.jar is packaged now, is that the teiid-web-console.zip gets included as a dependency. > {code} > [INFO] +- org.jboss.teiid:teiid:jar:jdbc:8.12.5.redhat-2:compile > [INFO] | \- org.jboss.teiid.web-console:teiid-console-dist:zip:jboss-as7:2.5.6.Final-redhat-63-4:compile > {code} > And that becomes an issue when other external projects to Teiid include the jdbc driver as a dependency, in that they also end up requiring the web-console.zip. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4094) Move the packaging of teiid-jdbc.jar into is own project

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4094?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4094: ------------------------------------ Ok, so this was fixed post 8.12. > Move the packaging of teiid-jdbc.jar into is own project > -------------------------------------------------------- > > Key: TEIID-4094 > URL: https://issues.jboss.org/browse/TEIID-4094 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.5 > > > The issue with the way the teiid-jdbc.jar is packaged now, is that the teiid-web-console.zip gets included as a dependency. > {code} > [INFO] +- org.jboss.teiid:teiid:jar:jdbc:8.12.5.redhat-2:compile > [INFO] | \- org.jboss.teiid.web-console:teiid-console-dist:zip:jboss-as7:2.5.6.Final-redhat-63-4:compile > {code} > And that becomes an issue when other external projects to Teiid include the jdbc driver as a dependency, in that they also end up requiring the web-console.zip. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4024) Server fails to shutdown if vdb with REST service generation is deployed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4024?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4024: ---------------------------------- Fix Version/s: 8.13.3 (was: 8.13.x) > Server fails to shutdown if vdb with REST service generation is deployed > ------------------------------------------------------------------------ > > Key: TEIID-4024 > URL: https://issues.jboss.org/browse/TEIID-4024 > Project: Teiid > Issue Type: Bug > Components: VDB > Affects Versions: 8.12.5 > Environment: DV 6.3 ER1 > Reporter: Filip Elias > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.3 > > Attachments: nosource-vdb.xml, server_trace.log > > > DV sometimes won't stop if vdb with REST service generation is deployed. > Server log is in the attachment. > When the server is killed and started again, it will stop correctly. > The issue is random. Server fails to stop in 50% of cases. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2016