June 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2992) MongoDB: Offset clause causes MongoDB to crash

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2992?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2992: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1105473|https://bugzilla.redhat.com/show_bug.cgi?id=1105473] from NEW to MODIFIED > MongoDB: Offset clause causes MongoDB to crash > ---------------------------------------------- > > Key: TEIID-2992 > URL: https://issues.jboss.org/browse/TEIID-2992 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.4.1 > Environment: MongoDB < 2.5.2 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.7.1, 8.8 > > > MongoDB(version < 2.5.2) will crash when offset clause is used in SQL query. > Althought the bug[1] is in MongoDB (Adding big number into $limit causes Mongodb to shutdown), it is also caused by teiid because it adds max integer into $limit which seems to be unnecessary. > Sample query: > {code} > SELECT INTKEY FROM bqt1.smalla ORDER BY INTKEY OFFSET 45 ROWS > {code} > Generated mongo command: > {code} > { aggregate: "smalla", pipeline: [ { $project: { c_0: "$INTKEY" } }, { $sort: { c_0: 1 } }, { $skip: 45 }, { $limit: 2147483647 } ] } > {code} > [1] https://jira.mongodb.org/browse/SERVER-10136 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2988) MongoDB: Function substring - starting index and number of arguments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2988?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2988: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1105101|https://bugzilla.redhat.com/show_bug.cgi?id=1105101] from NEW to MODIFIED > MongoDB: Function substring - starting index and number of arguments > -------------------------------------------------------------------- > > Key: TEIID-2988 > URL: https://issues.jboss.org/browse/TEIID-2988 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.7.1, 8.8 > > > Two minor bugs in function substring() > Mongo's function $substr takes only 3 arguments so this query fails: > {code} > SELECT intkey, SUBSTRING(BQT1.SmallA.stringkey, 1) FROM BQT1.SmallA ORDER BY intkey > {code} > {code} > Exception:13:18:48,220 ERROR [org.teiid.CONNECTOR] (Worker38_QueryProcessorQueue345) Connector worker process failed for atomic-request=omsmHP0o16Sa.40.0.86: com.mongodb.CommandFailureException: { "serverUsed" : "localhost/127.0.0.1:27017" , "errmsg" : "exception: the $substr operator requires 3 operand(s)" , "code" : 16020 , "ok" : 0.0} > at com.mongodb.CommandResult.getException(CommandResult.java:71) > at com.mongodb.CommandResult.throwOnError(CommandResult.java:110) > at com.mongodb.DBCollection.aggregate(DBCollection.java:1308) > {code} > Generated mongo command: > {code} > { aggregate: "smalla", pipeline: [ { $project: { c_0: "$INTKEY", c_1: { $substr: [ "$STRINGKEY", 1 ] } } }, { $sort: { c_0: 1 } } ] } > {code} > Mongo's $substr function second argument represents number of bytes to skip, not the starting index. The function substring(StringKey,1,1) returns the second letter, but it should return the first letter. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2987) MongoDB: No rows are returned when a function is used in a where clause

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2987?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2987: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1105087|https://bugzilla.redhat.com/show_bug.cgi?id=1105087] from NEW to MODIFIED > MongoDB: No rows are returned when a function is used in a where clause > ----------------------------------------------------------------------- > > Key: TEIID-2987 > URL: https://issues.jboss.org/browse/TEIID-2987 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.4.1 > Environment: Teiid 8.4.1 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.7.1, 8.8 > > > Teiid will return no rows when a function which is pushed down is used in a where clause. > These queries should return few rows, but the result is empty: > Query: > {code} > SELECT intkey, stringnum FROM BQT1.SmallA WHERE concat(stringkey, stringnum) = '7-17' ORDER BY intkey > {code} > Generated mongo command: > {code} > {aggregate: "smalla", pipeline: [ { $match: { _m0: "7-17" } }, { $project: { c_0: "$INTKEY", c_1: "$STRINGNUM" } }, { $sort: { c_0: 1 } } ] } > {code} > Query: > {code} > select intKey from bqt1.smalla where intKey+intKey >20 > {code} > Generated mongo command: > {code} > {aggregate: "smalla", pipeline: [ { $match: { _m0: { $gt: 20 } } }, { $project: { _m1: "$INTKEY" } } ] } > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2983) MongoDB: Function "count()" returns sum instead of number of rows

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2983?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2983: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1104614|https://bugzilla.redhat.com/show_bug.cgi?id=1104614] from ASSIGNED to MODIFIED > MongoDB: Function "count()" returns sum instead of number of rows > ----------------------------------------------------------------- > > Key: TEIID-2983 > URL: https://issues.jboss.org/browse/TEIID-2983 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.7.1, 8.8 > > > Function "count()" returns sum of rows instead of number of rows > Query [1] returns sum of values of all rows of IntKey column. > Query [2] correctly returns number of rows > > [1] SELECT COUNT(IntKey) FROM BQT1.SmallA > [2] SELECT COUNT(*) FROM BQT1.SmallA -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2984) MongoDB: Usage of function "mod()" in SQL query throws an exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2984?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2984: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1104758|https://bugzilla.redhat.com/show_bug.cgi?id=1104758] from ASSIGNED to MODIFIED > MongoDB: Usage of function "mod()" in SQL query throws an exception > ------------------------------------------------------------------- > > Key: TEIID-2984 > URL: https://issues.jboss.org/browse/TEIID-2984 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.8 > > Attachments: server.log > > > Exception[1] is thrown when function modulo(mod) is used in SQL query. > Sample query: > SELECT LongNum, 11, MOD(LongNum, 11) FROM BQT1.SmallA ORDER BY LONGNUM > Server log is in the attachment. > [1] 16:36:59,645 ERROR [org.teiid.CONNECTOR] (Worker10_QueryProcessorQueue71) Connector worker process failed for atomic-request=hRCP8hHjrmZb.25.0.13: com.mongodb.CommandFailureException: { "serverUsed" : "localhost/127.0.0.1:27017" , "errmsg" : "exception: disallowed field type Array in object expression (at 'mod')" , "code" : 15992 , "ok" : 0.0} > at com.mongodb.CommandResult.getException(CommandResult.java:71) > at com.mongodb.CommandResult.throwOnError(CommandResult.java:110) > at com.mongodb.DBCollection.aggregate(DBCollection.java:1308) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3013) Add realm authentication to teiid-security

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3013: ------------------------------------- Summary: Add realm authentication to teiid-security Key: TEIID-3013 URL: https://issues.jboss.org/browse/TEIID-3013 Project: Teiid Issue Type: Quality Risk Security Level: Public (Everyone can see) Components: Server Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7.1, 8.8 To allow teiid to use users added by the console by default we should add the RealmDirect login module to the teiid-security security domain. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1675) Add capability to insert/update/delete multi-value attributes in LDAP connector

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1675?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1675. ----------------------------------- Fix Version/s: 8.8 (was: Open To Community) (was: 8.9) Resolution: Done Added multi-value attribute to primarily string array mapping support. This also allows for insert/update. Updated the docs with an insert example. The existing multivalue concat logic using the column default value was left as is for backwards compatibility - but it is definitely not the best mechanism as there is no escaping performed on values containing the delimiter and mispurposes the default value. > Add capability to insert/update/delete multi-value attributes in LDAP connector > ------------------------------------------------------------------------------- > > Key: TEIID-1675 > URL: https://issues.jboss.org/browse/TEIID-1675 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: LDAP Connector > Affects Versions: 7.4 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.8 > > > Add ability to insert/update/delete multi-value attributes through the LDAP connector. For example, this would present the opportunity for maintaining group membership through modifying the list of member attribute values in an LDAP groupOfNames object. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2647) Add an impala translator

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2647?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2647: ------------------------------------ http://www.cloudera.com/content/cloudera-content/cloudera-docs/Impala/lat... > Add an impala translator > ------------------------ > > Key: TEIID-2647 > URL: https://issues.jboss.org/browse/TEIID-2647 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: alpha1 > Fix For: 8.7.1, 8.8 > > > Impala offers an alternative to Hive SQL access: > http://blog.cloudera.com/blog/2012/10/cloudera-impala-real-time-queries-i... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2982) Allow to change visibility to a model from imported vdb

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2982?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2982: --------------------------------------- > If possible I would like to see Teiid supports overriding 'metadata' (DDL for us) for model too. There are some design considerations there. Right now we think of a vdb import as imorting the operational vdb state. That is the model is the same for all importing vdbs - the metadata, translator, etc. are shared. If we have an importing vdb override the metadata, this would have to be a different sort of operation - a reuse of the metadata, rather than the operational state. > Allow to change visibility to a model from imported vdb > ------------------------------------------------------- > > Key: TEIID-2982 > URL: https://issues.jboss.org/browse/TEIID-2982 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 8.7 > Reporter: Kenichi Takemura > Assignee: Steven Hawkins > > When a new vdb uses import-vdb, changing(override) visibility to a model from imported vdb would need to hide non-related model to the new vdb. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2982) Allow to change visibility to a model from imported vdb

by Kenichi Takemura (JIRA)

[ https://issues.jboss.org/browse/TEIID-2982?page=com.atlassian.jira.plugin... ] Kenichi Takemura commented on TEIID-2982: ----------------------------------------- Hi Thanks guys! I am fine with the second one. If possible I would like to see Teiid supports overriding 'metadata' (DDL for us) for model too. I am happy to have more overriding features added by different issues created later but considering further supports in this fix (I mean design perspective), that might be helpful. Thanks > Allow to change visibility to a model from imported vdb > ------------------------------------------------------- > > Key: TEIID-2982 > URL: https://issues.jboss.org/browse/TEIID-2982 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 8.7 > Reporter: Kenichi Takemura > Assignee: Steven Hawkins > > When a new vdb uses import-vdb, changing(override) visibility to a model from imported vdb would need to hide non-related model to the new vdb. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 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 2014