October 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3166) Allow allowDiskUse setting in MongoDB translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3166?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3166: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Allow allowDiskUse setting in MongoDB translator > ------------------------------------------------ > > Key: TEIID-3166 > URL: https://issues.jboss.org/browse/TEIID-3166 > Project: Teiid > Issue Type: Enhancement > Reporter: Harrison Gentry > Assignee: Ramesh Reddy > Priority: Minor > > When querying a MongoDB, steps of computation are limited to 100MiB. Querying large databases can easily exceed this limit, so usually allowDiskUse:true is passed in the aggregate query: > http://docs.mongodb.org/manual/reference/command/aggregate/ > In Teiid, however, there is currently no way to specify this with SQL. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3163) Add TEXTTABLE capability to support Custom Line Separator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3163?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3163: ---------------------------------- Fix Version/s: 8.10 > Add TEXTTABLE capability to support Custom Line Separator > ---------------------------------------------------------- > > Key: TEIID-3163 > URL: https://issues.jboss.org/browse/TEIID-3163 > Project: Teiid > Issue Type: Enhancement > Environment: Teiid 8.8.0.Final > Reporter: Shiveeta Mattoo > Assignee: Steven Hawkins > Labels: FileConnector, TEXTTABLE > Fix For: 8.10 > > > Add TEXTTABLE capability to support Custom Line Separator -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3164) Second connection to VDB through Kerberos authentication ends with exception

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3164?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3164: --------------------------------------- Ramesh do you still have an appropriate test environment to look at this in? > Second connection to VDB through Kerberos authentication ends with exception > ---------------------------------------------------------------------------- > > Key: TEIID-3164 > URL: https://issues.jboss.org/browse/TEIID-3164 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora20 > arch: x86_64 > java: sun 1.7 > kdc: on localhost > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Second (third,forth,...) conection to VDB through Kerberos ends with exception: > javax.security.auth.login.LoginException: TEIID50103 Wrong Response returned from EXAMPLE.COM security domain; Expecting a Kerberoes response -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3166) Allow allowDiskUse setting in MongoDB translator

by Harrison Gentry (JIRA)

Harrison Gentry created TEIID-3166: -------------------------------------- Summary: Allow allowDiskUse setting in MongoDB translator Key: TEIID-3166 URL: https://issues.jboss.org/browse/TEIID-3166 Project: Teiid Issue Type: Enhancement Reporter: Harrison Gentry Assignee: Steven Hawkins Priority: Minor When querying a MongoDB, steps of computation are limited to 100MiB. Querying large databases can easily exceed this limit, so usually allowDiskUse:true is passed in the aggregate query: http://docs.mongodb.org/manual/reference/command/aggregate/ In Teiid, however, there is currently no way to specify this with SQL. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3166) Allow allowDiskUse setting in MongoDB translator

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3166?page=com.atlassian.jira.plugin... ] SBS JIRA Integration updated TEIID-3166: ---------------------------------------- Forum Reference: https://developer.jboss.org/thread/249390, https://developer.jboss.org/message/906437#906437 (was: https://developer.jboss.org/thread/249390) > Allow allowDiskUse setting in MongoDB translator > ------------------------------------------------ > > Key: TEIID-3166 > URL: https://issues.jboss.org/browse/TEIID-3166 > Project: Teiid > Issue Type: Enhancement > Reporter: Harrison Gentry > Assignee: Steven Hawkins > Priority: Minor > > When querying a MongoDB, steps of computation are limited to 100MiB. Querying large databases can easily exceed this limit, so usually allowDiskUse:true is passed in the aggregate query: > http://docs.mongodb.org/manual/reference/command/aggregate/ > In Teiid, however, there is currently no way to specify this with SQL. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3070) Netty worker threads cause system high cpu

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3070?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3070: --------------------------------------- > Teiid 8.7.x use bom to contorl netty version, as Bugzilla updates, the issue being handled in wildfly and EAP upstream, no changes are needed in teiid side. I know there are no changes on our side, but I would like to refer the community to a netty artifact with patching instructions for EAP 6.1 Alpha. > for current master netty 8.9, I have tested update netty version to 3.6.10, but execute build failed(runtime unit test failed), do you think we need upgrate the netty version? if yes, I will do more investigation. If there are test failures with an updated version, then yes we need to look at it more to determine if they are netty related. > Netty worker threads cause system high cpu > ------------------------------------------ > > Key: TEIID-3070 > URL: https://issues.jboss.org/browse/TEIID-3070 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7 > Environment: JDV 6.1.0.DR2 > JDV 6.0 > Reporter: Kylin Soong > Assignee: Kylin Soong > > I have hit this issue many times in deploying a VDB to JDV, All CPU be used by netty worker threads: > ~~~ > "New I/O worker #3" daemon prio=10 tid=0x00007fc71c0d2000 nid=0x320b runnable [0x00007fc7074f3000] > java.lang.Thread.State: RUNNABLE > at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) > at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269) > at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:79) > at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:87) > - locked <0x00000000c42b4318> (a sun.nio.ch.Util$2) > - locked <0x00000000c42b4328> (a java.util.Collections$UnmodifiableSet) > - locked <0x00000000c42b42d0> (a sun.nio.ch.EPollSelectorImpl) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:98) > at org.jboss.netty.channel.socket.nio.SelectorUtil.select(SelectorUtil.java:64) > ~~~ > Seems this is a exist netty issue, search "jboss netty high cpu" via google we can get lots of result. > Below link have detailed depiction about this issue; > https://github.com/kylinsoong/teiid-samples/tree/master/highcpu -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3165) TeiidDataSource ignores jassName

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3165?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3165: --------------------------------------- Looks like these are only being added in the case of a non-socket connection. > TeiidDataSource ignores jassName > -------------------------------- > > Key: TEIID-3165 > URL: https://issues.jboss.org/browse/TEIID-3165 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora 20 > arch: x86_64 > java: sun 1.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > I am trying to connect to VDB through Kerberos authentication using TeiidDataSource: > TeiidDataSource tds = new TeiidDataSource(); > tds.setServerName("localhost"); > tds.setPortNumber(31000); > tds.setDatabaseName(<vdb>); > tds.setJaasName(<jassName>); > tds.setKerberosServicePrincipleName(<principalName>); > but tds.getConnection(); ends with: > TEIID20005 Client URL connection property missing "jaasName". Please add the property to connection URL > Connection through TeiidDriver works fine: > url: jdbc:teiid:<vdb>@mm://<host>:31000;jaasName=<jassName>;kerberosServicePrincipleName=<principalName> -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3165) TeiidDataSource ignores jassName

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-3165: ----------------------------------- Summary: TeiidDataSource ignores jassName Key: TEIID-3165 URL: https://issues.jboss.org/browse/TEIID-3165 Project: Teiid Issue Type: Bug Affects Versions: 8.7.1 Environment: OS: fedora 20 arch: x86_64 java: sun 1.7 Reporter: Juraj Duráni Assignee: Steven Hawkins I am trying to connect to VDB through Kerberos authentication using TeiidDataSource: TeiidDataSource tds = new TeiidDataSource(); tds.setServerName("localhost"); tds.setPortNumber(31000); tds.setDatabaseName(<vdb>); tds.setJaasName(<jassName>); tds.setKerberosServicePrincipleName(<principalName>); but tds.getConnection(); ends with: TEIID20005 Client URL connection property missing "jaasName". Please add the property to connection URL Connection through TeiidDriver works fine: url: jdbc:teiid:<vdb>@mm://<host>:31000;jaasName=<jassName>;kerberosServicePrincipleName=<principalName> -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3164) Second connection to VDB through Kerberos authentication ends with exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3164?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3164: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1151027 > Second connection to VDB through Kerberos authentication ends with exception > ---------------------------------------------------------------------------- > > Key: TEIID-3164 > URL: https://issues.jboss.org/browse/TEIID-3164 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora20 > arch: x86_64 > java: sun 1.7 > kdc: on localhost > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Second (third,forth,...) conection to VDB through Kerberos ends with exception: > javax.security.auth.login.LoginException: TEIID50103 Wrong Response returned from EXAMPLE.COM security domain; Expecting a Kerberoes response -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3164) Second connection to VDB through Kerberos authentication ends with exception

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3164?page=com.atlassian.jira.plugin... ] Juraj Duráni updated TEIID-3164: -------------------------------- Steps to Reproduce: 1. Comfigure Kerberos authentication with Teiid over JDBC (https://developer.jboss.org/wiki/APracticalhow-toGuideToKerberosAuthentic...) - do not set default Kerberos authentication for teiid-jdbc port: <transport name="jdbc" socket-binding="teiid-jdbc" protocol="teiid"> <authentication security-domain="teiid-security"/> </transport> 2. Create dynamic VDB and add required properties to define Kerberos authentication (https://docs.jboss.org/author/display/teiid88final/Kerberos+support+throu...) 3. Connect to VDB and run any query (e.g. SELECT VDBName FROM SYS.Schemas) 4. First attempt should return correct result 5. Second ends with exception was: 1. Comfigure Kerberos authentication with Teiid over JDBC (https://developer.jboss.org/wiki/APracticalhow-toGuideToKerberosAuthentic...) - do not set default Kerberos authentication for teiid-jdbc port: <transport name="jdbc" socket-binding="teiid-jdbc" protocol="teiid"> <authentication security-domain="teiid-security"/> </transport> 2. Create dynamic VDB and add required properties to define Kerberos authentication (https://docs.jboss.org/author/display/teiid88final/Kerberos+support+throu...) 3. Connect to VDB and run any query (e.g. SELECT VDBName FROM SYS.Schemas) 4. First attempt should return correct result 5. Second ends with exception > Second connection to VDB through Kerberos authentication ends with exception > ---------------------------------------------------------------------------- > > Key: TEIID-3164 > URL: https://issues.jboss.org/browse/TEIID-3164 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora20 > arch: x86_64 > java: sun 1.7 > kdc: on localhost > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Second (third,forth,...) conection to VDB through Kerberos ends with exception: > javax.security.auth.login.LoginException: TEIID50103 Wrong Response returned from EXAMPLE.COM security domain; Expecting a Kerberoes response -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2014