July 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3474) Inconsistent results of RIGHT function for different datasources

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3474?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3474: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1221051|https://bugzilla.redhat.com/show_bug.cgi?id=1221051] from ON_QA to VERIFIED > Inconsistent results of RIGHT function for different datasources > ---------------------------------------------------------------- > > Key: TEIID-3474 > URL: https://issues.jboss.org/browse/TEIID-3474 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.7 > Environment: OS: Fedora 20 > arch: x86_64 > java: oracle 1.8 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.11 > > > The RIGHT function returns different results for different datasources. Some of those results are inconsistent with definition of the RIGHT(x,y) function. > ======= > +*Query: SELECT intkey, RIGHT(intkey, 1) FROM table ORDER BY intkey*+ > *Teradata, SQLServer, Sybase, Ingres, MySQL, Oracle (this result is OK):* > 0 0 > 1 1 > 2 2 > ... > 10 0 > 11 1 > ... > 100 0 > 101 1 > *Postgres:* > 0 0 > 1 1 > 2 2 > ... > 10 10 > 11 11 > ... > 100 100 > 101 101 > *DB2:* > 0 " " > 1 " " > 2 " " > ... > 10 " " > 11 " " > ... > 100 " " > 101 " " > ===== > +*Query:SELECT intkey, RIGHT(intkey, 2) FROM table ORDER BY intkey*+ > *SQLServer, Sybase, Ingress, MySQL, Teradata (this result is OK):* > 0 0 > 1 1 > ... > 10 10 > 11 11 > ... > 100 00 > 101 01 > *Oracle:* > 0 <null> > 1 <null> > 2 <null> > ... > 10 10 > 11 11 > ... > 100 00 > 101 01 > *Postgres:* > 0 0 > 1 1 > 2 2 > ... > 10 10 > 11 11 > ... > 100 100 > 101 101 > *DB2:* > 0 " " > 1 " " > 2 " " > ... > 10 " " > 11 " " > ... > 100 " " > 101 " " -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3358) Issues with entity set names

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3358?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3358: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1208515|https://bugzilla.redhat.com/show_bug.cgi?id=1208515] from ON_QA to VERIFIED > Issues with entity set names > ---------------------------- > > Key: TEIID-3358 > URL: https://issues.jboss.org/browse/TEIID-3358 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.7.1.6_2, 8.11, 8.7.3 > > > The entity set name used for sql generation should be the fully qualified name. If there is for example two table with the same names in schemas visible to odata, but one of the tables does not have a key, then an ambiguous name exception will be thrown if an odata url is used with only the base table name. > It also appears that the URI link in the results metadata uses the non-qualified table name, which will have issues in the scenario above. > We may also need to document or add an additional check for ambiguity as the OData4j findEdmEntitySet logic will return the first matching entity, which is generally against our approach to resolving. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3410) OData object URI does not resolve to a usable URL.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3410?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3410: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1208515|https://bugzilla.redhat.com/show_bug.cgi?id=1208515] from ON_QA to VERIFIED > OData object URI does not resolve to a usable URL. > -------------------------------------------------- > > Key: TEIID-3410 > URL: https://issues.jboss.org/browse/TEIID-3410 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.11 > > > OData object URI does not resolve to a usable URL. When accessing a VDB via odata with a browser either via JSON or XML the uri listed in the metadata is not valid, it doesn't have the FQN of the table, only the type shows FQN: > "__metadata" : { > "uri" : "http://localhost:8080/odata/ODataRHQ/rhq_agent(10001)", > "type" : "RHQ32.rhq_agent" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3407) Clarify in the README's for each quickstart regarding how to start the server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3407?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3407: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1190678|https://bugzilla.redhat.com/show_bug.cgi?id=1190678] from ON_QA to VERIFIED > Clarify in the README's for each quickstart regarding how to start the server > ----------------------------------------------------------------------------- > > Key: TEIID-3407 > URL: https://issues.jboss.org/browse/TEIID-3407 > Project: Teiid > Issue Type: Enhancement > Components: Quick Starts > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Trivial > > Change the start command in the README's to be the following: > To start the server, open a command line and navigate to the "bin" directory under the root directory of the JBoss server and run: > > For Linux: ./standalone.sh > for Windows: standalone.bat > append the following to the command to indicate which configuration to use if Teiid isn't configured in the default configuration > > -c standalone-teiid.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3408) Update the quickstarts that refer to using user .properties files and user roles files

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3408?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3408: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1190678|https://bugzilla.redhat.com/show_bug.cgi?id=1190678] from ON_QA to VERIFIED > Update the quickstarts that refer to using user .properties files and user roles files > -------------------------------------------------------------------------------------- > > Key: TEIID-3408 > URL: https://issues.jboss.org/browse/TEIID-3408 > Project: Teiid > Issue Type: Bug > Components: Quick Starts > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > > Update the quoickstarts that still refer to using user security .properties and user roles files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3406) Upgrade quickstarts to use Teiid 8.10.0-Final and use IP BOM 26

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3406?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3406: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1190683|https://bugzilla.redhat.com/show_bug.cgi?id=1190683] from ON_QA to VERIFIED > Upgrade quickstarts to use Teiid 8.10.0-Final and use IP BOM 26 > --------------------------------------------------------------- > > Key: TEIID-3406 > URL: https://issues.jboss.org/browse/TEIID-3406 > Project: Teiid > Issue Type: Task > Components: Quick Starts > Reporter: Van Halbert > Assignee: Van Halbert > > Upgrade quickstarts to be based on IP Bom 26 and Teiid 8.10.0-Fina. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3578) server becomes unresponsive after running for a while

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3578?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-3578: ------------------------------------ TEIID-3404 is related to DatabaseAppender consume high cpu, but seems this issue no high cpu problem. Also the EJB persist thread also in wait status, that seems no more logger record need to persist. > server becomes unresponsive after running for a while > ----------------------------------------------------- > > Key: TEIID-3578 > URL: https://issues.jboss.org/browse/TEIID-3578 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1 > Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA > JBoss Data Virtualization 6.1.0.ER4 > Reporter: Jorge Herrera > Assignee: Steven Hawkins > Attachments: server.log, stackTrace_TEIID-3578, threaddump.txt > > > Server becomes unresponsive, it does ack new sessions, but nothing else, admin-console, and direct queries are completely unresponsive. If I reboot the server it works just fine. Disk space / RAM / CPU all seem just fine. > [root@BIJDVDev2 ~]# df > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/xvde1 6062016 4601808 1397596 77% / > none 7619624 0 7619624 0% /dev/shm > [BIJDVDev2.dev.a1.vary.redhat.com] [11:38:48 AM] > [root@BIJDVDev2 ~]# top > top - 11:43:05 up 14 days, 13:31, 1 user, load average: 0.00, 0.00, 0.00 > Tasks: 151 total, 1 running, 150 sleeping, 0 stopped, 0 zombie > Cpu(s): 0.1%us, 0.1%sy, 0.0%ni, 99.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st > Mem: 15239248k total, 5387488k used, 9851760k free, 203540k buffers > Swap: 0k total, 0k used, 0k free, 2887904k cached -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3578) server becomes unresponsive after running for a while

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3578?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3578: --------------------------------------- In both cases their is nothing that is actively holding the lock - all threads are waiting. The database appender looks to also be having an issue, which could be contributing to the logging backup. Are you using asynch appenders and if so is it set to block once it reaches a certain queue depth? > server becomes unresponsive after running for a while > ----------------------------------------------------- > > Key: TEIID-3578 > URL: https://issues.jboss.org/browse/TEIID-3578 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1 > Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA > JBoss Data Virtualization 6.1.0.ER4 > Reporter: Jorge Herrera > Assignee: Steven Hawkins > Attachments: server.log, stackTrace_TEIID-3578, threaddump.txt > > > Server becomes unresponsive, it does ack new sessions, but nothing else, admin-console, and direct queries are completely unresponsive. If I reboot the server it works just fine. Disk space / RAM / CPU all seem just fine. > [root@BIJDVDev2 ~]# df > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/xvde1 6062016 4601808 1397596 77% / > none 7619624 0 7619624 0% /dev/shm > [BIJDVDev2.dev.a1.vary.redhat.com] [11:38:48 AM] > [root@BIJDVDev2 ~]# top > top - 11:43:05 up 14 days, 13:31, 1 user, load average: 0.00, 0.00, 0.00 > Tasks: 151 total, 1 running, 150 sleeping, 0 stopped, 0 zombie > Cpu(s): 0.1%us, 0.1%sy, 0.0%ni, 99.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st > Mem: 15239248k total, 5387488k used, 9851760k free, 203540k buffers > Swap: 0k total, 0k used, 0k free, 2887904k cached -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3492) Provide a mechanism for users to modify the salesforce api version

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3492?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3492: ------------------------------------- Ok, I tried adding a different versions of the the "com.force.api" libraries to the build such that one can easily add a new version, however it proved impossible with current build system. So, I opted to keep to keep at the same version, but moved the "com.force.api" to separate module, such that a user can easily provide a new module and configure the translator and resource-adapter to use the new module. The pull for changes is here https://github.com/teiid/teiid/pull/494 I am not completely convinced that there are no other alternatives, but can't think of any right now. > Provide a mechanism for users to modify the salesforce api version > ------------------------------------------------------------------ > > Key: TEIID-3492 > URL: https://issues.jboss.org/browse/TEIID-3492 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > We should provide a mechanism to easily target a different salesforce api version. We are currently defaulting to v22, which is quite old. The version change must be controlled as the metadata and the sf jars can be incompatible - if you for example build a model from v22, then you must stay on v22, and then recreate the model once you want to move to a later version. > Currently the update procedure would be to copy/modify the salesforce translator module and have it point to newer wsc and partner api jars (which are java api compatible from what I have seen) and then change the any salesforce resource adapters to use the new api url. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3578) server becomes unresponsive after running for a while

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3578?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3578: ------------------------------------- There seems more threads locked during accessing the service registry. > server becomes unresponsive after running for a while > ----------------------------------------------------- > > Key: TEIID-3578 > URL: https://issues.jboss.org/browse/TEIID-3578 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1 > Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA > JBoss Data Virtualization 6.1.0.ER4 > Reporter: Jorge Herrera > Assignee: Steven Hawkins > Attachments: server.log, stackTrace_TEIID-3578, threaddump.txt > > > Server becomes unresponsive, it does ack new sessions, but nothing else, admin-console, and direct queries are completely unresponsive. If I reboot the server it works just fine. Disk space / RAM / CPU all seem just fine. > [root@BIJDVDev2 ~]# df > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/xvde1 6062016 4601808 1397596 77% / > none 7619624 0 7619624 0% /dev/shm > [BIJDVDev2.dev.a1.vary.redhat.com] [11:38:48 AM] > [root@BIJDVDev2 ~]# top > top - 11:43:05 up 14 days, 13:31, 1 user, load average: 0.00, 0.00, 0.00 > Tasks: 151 total, 1 running, 150 sleeping, 0 stopped, 0 zombie > Cpu(s): 0.1%us, 0.1%sy, 0.0%ni, 99.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st > Mem: 15239248k total, 5387488k used, 9851760k free, 203540k buffers > Swap: 0k total, 0k used, 0k free, 2887904k cached -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2015