February 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3327) Connect for OSIsoft PI

by Albert Wong (JIRA)

Albert Wong created TEIID-3327: ---------------------------------- Summary: Connect for OSIsoft PI Key: TEIID-3327 URL: https://issues.jboss.org/browse/TEIID-3327 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Reporter: Albert Wong Assignee: Steven Hawkins Priority: Optional We have several customers that are using OSIsoft to get time sliced data. We'd like JDV/Teiid to be able to pull data from OSIsoft (OSIsoft is a data source for JDV/Teiid). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2903) Dynamic VDB with Google Spreadsheet source - no metadata

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2903?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2903: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1109421|https://bugzilla.redhat.com/show_bug.cgi?id=1109421] from VERIFIED to CLOSED > Dynamic VDB with Google Spreadsheet source - no metadata > --------------------------------------------------------- > > Key: TEIID-2903 > URL: https://issues.jboss.org/browse/TEIID-2903 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Steven Hawkins > Fix For: 8.7, 8.4.4 > > > Deployed Dynamic VDB with Google Spreadsheet source. This is in the server log: > 16:17:49,286 WARN [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 2) TEIID31070 Empty model;There are no tables, procedures or functions defined in this model importVDBSrcModel > According to the translator docs https://docs.jboss.org/author/display/TEIID/Google+Spreadsheet+Translator "There are no google-spreadsheet importer settings, but it does provide metadata for dynamic VDBs." > No metadata is returned. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3317) MongoDB: group by doesn't work with MongoDB 2.6.3

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3317?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3317: --------------------------------------- Can you test against an 8.10 pre-release? It looks like this may be a duplicate of TEIID-3235 > MongoDB: group by doesn't work with MongoDB 2.6.3 > -------------------------------------------------- > > Key: TEIID-3317 > URL: https://issues.jboss.org/browse/TEIID-3317 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.9.1 > Environment: Teiid 8.9.1 with MongoDB version: 2.6.3 using MongoDB Driver mongo-java-driver-2.12.3.jar > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Labels: Teiid > > Running group by sql through exception: > select "FirstName" > from "MongoDB_Array_263"."TeiidArray" > group by "FirstName" > order by "FirstName" > limit 1000 > Exception: > Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 > at java.util.ArrayList.rangeCheck(ArrayList.java:604) > at java.util.ArrayList.get(ArrayList.java:382) > at org.teiid.translator.mongodb.MongoDBQueryExecution.next(MongoDBQueryExecution.java:132) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:386) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:204) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:209) > at $Proxy182.more(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:301) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3326) Add back a drools quick start

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3326?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3326: --------------------------------------- Van is this something that you can take? > Add back a drools quick start > ----------------------------- > > Key: TEIID-3326 > URL: https://issues.jboss.org/browse/TEIID-3326 > Project: Teiid > Issue Type: Quality Risk > Components: Quick Starts > Reporter: Steven Hawkins > > Add back a Drools quick start: https://docs.jboss.org/author/display/teiidexamples/Drools+Component+Inte... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3326) Add back a drools quick start

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3326: ------------------------------------- Summary: Add back a drools quick start Key: TEIID-3326 URL: https://issues.jboss.org/browse/TEIID-3326 Project: Teiid Issue Type: Quality Risk Components: Quick Starts Reporter: Steven Hawkins Add back a Drools quick start: https://docs.jboss.org/author/display/teiidexamples/Drools+Component+Inte... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2875) Metadata failed to load. No column found

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2875?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2875: --------------------------------------- Camilo you are seeing a related, but different issue. The import logic does not take into account Oracle nested tables, which appear to have an incomplete metadata representation in the JDBC DatabaseMetaData. As for the import properties, where were they set in the vdb? They should be children of the importing model. If you are sufficiently limiting your import, it should be successful. Also you more than likely want to leave importApproximateIndexes at the default of true. > Metadata failed to load. No column found > ---------------------------------------- > > Key: TEIID-2875 > URL: https://issues.jboss.org/browse/TEIID-2875 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.6 > Environment: Windows server 2003, Windows 7. > Reporter: SHI HONG CHIN > Assignee: Steven Hawkins > Attachments: JakkerData-vdb.xml > > > Affected database: Oracle > The following error displayed when Teiid loading a dynamic VDB: > 10:21:41,458 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB JakkerData.1 model "IWMS" metadata failed to load. Reason:TEIID60011 No column found with name "RATE"."CHARGE_NAME" > 10:23:29,994 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB JakkerData.1 model "IWMS" metadata failed to load. Reason:TEIID60011 No column found with name "RATE"."CHARGE_NAME" > I am not the one who design the database. But, I cannot find any table with above mentioned column name in Oracle database. So, I am not sure whether the above mentioned column name is a hidden column or not. > This bug does not exist in version 8.5. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3254) Add supporting capabilities

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3254?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3254: ---------------------------------- Fix Version/s: (was: 8.10) > Add supporting capabilities > --------------------------- > > Key: TEIID-3254 > URL: https://issues.jboss.org/browse/TEIID-3254 > Project: Teiid > Issue Type: Sub-task > Components: Connector API, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > With spreadsheet queries LIKE is not supported in UPDATE/DELETE and only simple values are supported in the update change set. > We should add capabilities to account for these restrictions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3254) Add supporting capabilities

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3254?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3254. ----------------------------------- Resolution: Won't Fix This is not needed for spreadsheets as the like/update literal restriction can only be worked around with compensation - which is not possible without a primary key and that will likely not be defined on a worksheet. > Add supporting capabilities > --------------------------- > > Key: TEIID-3254 > URL: https://issues.jboss.org/browse/TEIID-3254 > Project: Teiid > Issue Type: Sub-task > Components: Connector API, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > With spreadsheet queries LIKE is not supported in UPDATE/DELETE and only simple values are supported in the update change set. > We should add capabilities to account for these restrictions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3254) Add supporting capabilities

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3254?page=com.atlassian.jira.plugin... ] Work on TEIID-3254 stopped by Steven Hawkins. --------------------------------------------- > Add supporting capabilities > --------------------------- > > Key: TEIID-3254 > URL: https://issues.jboss.org/browse/TEIID-3254 > Project: Teiid > Issue Type: Sub-task > Components: Connector API, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > With spreadsheet queries LIKE is not supported in UPDATE/DELETE and only simple values are supported in the update change set. > We should add capabilities to account for these restrictions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3301) Add GEOMETRY_COLUMNS view

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3301?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3301: --------------------------------------- > JTS IO classes support 3d but last time I played with them they would drop the Z coordinate when writing WKT. Yes I've added a doc note and a check in GeomtryUtils.getGeometry to say that this implementation is effectively 2d. > Could we do blob concatenation in all cases to return SRID 32bit int + WKB? I've only tried it on MySQL so far but it seems like it should work on the others as well. As far as I know that could work for mysql/postgresql, but I'm not sure about oracle. However if there is much overhead for mysql, I would just rely on the internal storage format rather than a similar function based conversion. Also if the geometry value is being computed by a function/expression, the resulting sql could take a performance hit as the expression will be repeated. Which is why it seems simpler to stick with the ewkb result from postgresql. > Add GEOMETRY_COLUMNS view > ------------------------- > > Key: TEIID-3301 > URL: https://issues.jboss.org/browse/TEIID-3301 > Project: Teiid > Issue Type: Feature Request > Reporter: Tom Arnold > Assignee: Steven Hawkins > Labels: spatial > Fix For: 8.10 > > > Another OGC Simple Features implementation detail. Basically this is like a specialized version of SYS.COLUMNS, and would be used to support GIS software (like GeoServer). > http://www.carocoops.org/resources/doc/postgis/x321.html > {code} > CREATE TABLE GEOMETRY_COLUMNS ( > F_TABLE_CATALOG VARCHAR(256) NOT NULL, > F_TABLE_SCHEMA VARCHAR(256) NOT NULL, > F_TABLE_NAME VARCHAR(256) NOT NULL, > F_GEOMETRY_COLUMN VARCHAR(256) NOT NULL, > COORD_DIMENSION INTEGER NOT NULL, > SRID INTEGER NOT NULL, > TYPE VARCHAR(30) NOT NULL > ) > {code} > I think we could implement this by storing SRID & friends as column properties, and then creating a view on SYS.COLUMNS & SYS.PROPERTIES. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2015