September 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1244) JBoss AS admin console troubles with text based connection factory

by Aleksandar Kostadinov (JIRA)

JBoss AS admin console troubles with text based connection factory ------------------------------------------------------------------ Key: TEIID-1244 URL: https://jira.jboss.org/browse/TEIID-1244 Project: Teiid Issue Type: Bug Affects Versions: 7.1 Environment: RHEL5, openjdk, SOA-P 5.1dev3 Reporter: Aleksandar Kostadinov Assignee: Steven Hawkins When one deploys a text file based connection factory some issues are present to the user trying to use admin console to look at it. Go to Resources -> Connection Factories -> No Tx ConnectionFactories -> TextFileDS -> Control Tab Clicking on "test connection" returns a result of "No". Also server log shows an exception (see attached exception.txt). Clicking on "List Statistics" for the first time results in an exception (see attached exception_listStatistics.txt). If user clicks on "flush", then consequent calls to list statistics are successful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
6
0 / 0

[JBoss JIRA] Resolved: (TEIID-1156) Description fields for UDF Model objects are limited to 128 characters

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-1156?page=com.atlassian.jira.plugin.s... ] Steven Hawkins resolved TEIID-1156. ----------------------------------- Resolution: Done Checked with Barry that there are no issues with increasing the limit in Designer. Changed the base limit (function name / category) to 255 and the description limit to 4000. > Description fields for UDF Model objects are limited to 128 characters > ---------------------------------------------------------------------- > > Key: TEIID-1156 > URL: https://jira.jboss.org/browse/TEIID-1156 > Project: Teiid > Issue Type: Bug > Reporter: Barry LaFond > Assignee: Steven Hawkins > Fix For: 7.2 > > > While setting descriptions for the SalesForce UDF functions, I received validation errors stating that: "Description exceeds maximum length of: 128" > The com.metamatrix.query.function.metadata.FunctionMetadataValidator class has a hard-coded limit of 128. Noone seems to know why?? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-1156) Description fields for UDF Model objects are limited to 128 characters

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-1156?page=com.atlassian.jira.plugin.s... ] Steven Hawkins reassigned TEIID-1156: ------------------------------------- Assignee: Steven Hawkins > Description fields for UDF Model objects are limited to 128 characters > ---------------------------------------------------------------------- > > Key: TEIID-1156 > URL: https://jira.jboss.org/browse/TEIID-1156 > Project: Teiid > Issue Type: Bug > Reporter: Barry LaFond > Assignee: Steven Hawkins > Fix For: 7.2 > > > While setting descriptions for the SalesForce UDF functions, I received validation errors stating that: "Description exceeds maximum length of: 128" > The com.metamatrix.query.function.metadata.FunctionMetadataValidator class has a hard-coded limit of 128. Noone seems to know why?? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-982) Materialized Views should be treated as a service in MMx through the Console

by Ted Jones (JIRA)

[ https://jira.jboss.org/browse/TEIID-982?page=com.atlassian.jira.plugin.sy... ] Ted Jones reassigned TEIID-982: ------------------------------- Assignee: Ted Jones > Materialized Views should be treated as a service in MMx through the Console > ---------------------------------------------------------------------------- > > Key: TEIID-982 > URL: https://jira.jboss.org/browse/TEIID-982 > Project: Teiid > Issue Type: Feature Request > Components: Jopr Plugin > Reporter: Marc Shirley > Assignee: Ted Jones > Fix For: 7.1.1 > > > Should be a service, controlled in Console, logs controlled by Log Settings, viewable by Log Viewer. There should also be a way to verify success/failure, last run time, from within Console. This could also be linked into the scheduling service (JBEDSP-144) if that existed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-951) Add/Verify ipv6 readiness

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-951?page=com.atlassian.jira.plugin.sy... ] Ramesh Reddy resolved TEIID-951. -------------------------------- Resolution: Done Edit "run.conf" and add or modify to have these following parameters as Java properties java.net.preferIPv4Stack=false java.net.preferIPv6Addresses=true If your system does not already configured for IPv6, configure it so that it only assigns IPv6 address and then have DNS entry such that it can be used with "hostname", now start your JBoss AS as ./run.sh -b hostname That will make use of the IPv6 address underneath. In the Teiid JDBC URL, use the "hostname". If you do not have hostname, you are working directly with IPv6 bind address then use bind address in square brackets in JDBC URL like "[3ffe:ffff:100:f101::1]" as the hostname. If your system is not configured for IPv6, on Linux you can run following to test # setup two IPv6 addresses on two different interfaces MYTESTIP6_0=3ffe:ffff:0100:f101::1 # creating IP addresses echo "Creating address $MYTESTIP6_0 on eth0" ip -6 addr add $MYTESTIP6_0 dev eth0 # flush IPv6 tables echo "Flushing IPv6 tables" ip6tables -F Then start the JBoss AS as ./run.sh -b[3ffe:ffff:0100:f101::1] The access to the Teiid JDBC is same as defined above. > Add/Verify ipv6 readiness > ------------------------- > > Key: TEIID-951 > URL: https://jira.jboss.org/browse/TEIID-951 > Project: Teiid > Issue Type: Feature Request > Components: Documentation, Query Engine > Affects Versions: 6.2.0 > Reporter: Marc Shirley > Assignee: Ramesh Reddy > Fix For: 7.1.1 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Received request for ipv6 support to comply with Federal Government transition. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-217) LDAP Connector should provide a way to retrieve all values of an attribute that appears multiple times within a search result

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-217?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins updated TEIID-217: --------------------------------- Fix Version/s: 7.3 (was: 7.2) pushing to 7.3 > LDAP Connector should provide a way to retrieve all values of an attribute that appears multiple times within a search result > ----------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-217 > URL: https://jira.jboss.org/browse/TEIID-217 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 6.0.0 > Reporter: Michael Walker > Assignee: Michael Walker > Priority: Minor > Fix For: 7.3 > > > If an attribute appears more than once, we should have some way to return all values. Currently, we only return one value, with no rhyme, reason, or determinism as to which one gets returned. Implementing this is difficult when multiple attributes appear more than once, of course. But a simple example of where this problem rears it's head is in modeling LDAP groups. Groups typically have repeating attributes to represent each member, and it would be nice to query all members of a given group, but impossible to do so with the current logic. > A sophisticated solution would create a normalized view of a DN, breaking out multi-valued attributes into a separate table that could be joined by a primary key. A simple solution might allow attributes to be flagged as "multi-valued", in which case, they could be maintained in a single denormalized table that represents all values in the DN. > If we build an importer for LDAP, we should consider how to best handle this issue in the importer design. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-89) Data roles should account for the ability to create temp tables

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-89?page=com.atlassian.jira.plugin.sys... ] Steven Hawkins updated TEIID-89: -------------------------------- Fix Version/s: 7.3 (was: 7.2) pushing to 7.3 > Data roles should account for the ability to create temp tables > --------------------------------------------------------------- > > Key: TEIID-89 > URL: https://jira.jboss.org/browse/TEIID-89 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 7.3 > > > Defect Tracker #24698: Data roles should account for creating temp tables. Right now all temp table creation is allowed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-225) LDAP Connector should use base DN for table as base DN for updates as well as queries

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-225?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins updated TEIID-225: --------------------------------- Fix Version/s: 7.3 (was: 7.2) pushing to 7.3 > LDAP Connector should use base DN for table as base DN for updates as well as queries > ------------------------------------------------------------------------------------- > > Key: TEIID-225 > URL: https://jira.jboss.org/browse/TEIID-225 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 6.0.0 > Environment: MetaMatrix 5.5.3RC2 > Reporter: Greg Haber > Priority: Minor > Fix For: 7.3 > > > Ramesh had a great idea earlier today on the LDAP connector: > [Ramesh] Why not search base info along with PK information to build the unique > DN? That seems possible right? > [Greg] Yes, that is a great idea! I will put in a JIRA for that (small code change, changing name of "search base" to just "base", and doc change). Probably we should have both relative and fully qualified DNs accepted here. Note however that the base may be several levels higher up in the tree then where you want to put the entry, so the base DN may be "ou=people,dc=company,dc=com", with a relative DN of "uid=ghaber,ou=newyork" here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-231) Ability to support Connector Level UDF functions in the System

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-231?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins updated TEIID-231: --------------------------------- Fix Version/s: 7.3 (was: 7.2) pushing to 7.3 > Ability to support Connector Level UDF functions in the System > -------------------------------------------------------------- > > Key: TEIID-231 > URL: https://jira.jboss.org/browse/TEIID-231 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 7.3 > > > Currently we have UDF and Connector capabilities to define some custom functions in supported by a connector, however this is not seem less to deploy along with the connector, as connector functions do not support any parameters or design tools to define/declare them in CDK. We need a way to define and develop functions supported by a connector. > Suggestions. > 1) Use designer to define capabilities in a XMI file and attach with the connector, and let the server or MMQuery load these XMI files dynamically into the engine. > 2) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1090) Request to add a Google Apps/Calendar Connector

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-1090?page=com.atlassian.jira.plugin.s... ] Steven Hawkins updated TEIID-1090: ---------------------------------- Fix Version/s: 7.3 (was: 7.2) pushing to 7.3 > Request to add a Google Apps/Calendar Connector > ------------------------------------------------ > > Key: TEIID-1090 > URL: https://jira.jboss.org/browse/TEIID-1090 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Debbie Steigner > Fix For: 7.3 > > > Customer is requesting that we add a MetaMatrix Google Apps/Calendar Connector to a future release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 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 September 2010