December 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2321) The JdbcSslConfiguration incorrectly has property keymanagementAlgorithm set to false

by Van Halbert (JIRA)

Van Halbert created TEIID-2321: ---------------------------------- Summary: The JdbcSslConfiguration incorrectly has property keymanagementAlgorithm set to false Key: TEIID-2321 URL: https://issues.jboss.org/browse/TEIID-2321 Project: Teiid Issue Type: Bug Components: Build/Kits Affects Versions: 7.7.2 Reporter: Van Halbert Assignee: Steven Hawkins The primary issue is the line: <property name="keymanagementAlgorithm">false</property> The cause of the error message is because "false" is not a known KeyManagerFactory Algorithm. Suggestion is to comment out the property, and remove 'false' as the value. The Admin Guild Example 3.3 Configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2321) The JdbcSslConfiguration incorrectly has property keymanagementAlgorithm set to false

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2321?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2321: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=884763 > The JdbcSslConfiguration incorrectly has property keymanagementAlgorithm set to false > ------------------------------------------------------------------------------------- > > Key: TEIID-2321 > URL: https://issues.jboss.org/browse/TEIID-2321 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 7.7.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > > The primary issue is the line: > > <property name="keymanagementAlgorithm">false</property> > > The cause of the error message is because "false" is not a known KeyManagerFactory Algorithm. > Suggestion is to comment out the property, and remove 'false' as the value. > The Admin Guild Example 3.3 Configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2317) Primitive byte and char arrays always converted to binary/clob representation

by Stanley Roberts (JIRA)

Stanley Roberts created TEIID-2317: -------------------------------------- Summary: Primitive byte and char arrays always converted to binary/clob representation Key: TEIID-2317 URL: https://issues.jboss.org/browse/TEIID-2317 Project: Teiid Issue Type: Enhancement Components: Connector API Affects Versions: 8.2 Environment: Windows 7 x64 Reporter: Stanley Roberts Assignee: Steven Hawkins Teiid automatically converts char[] and byte[] to binary/clob representations as there are many cases where drivers return these values. That conversion is taking place however without consulting the target type. It would probably be better to delay this conversion for char[]/byte[] instances until an explicit cast is performed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
2
0 / 0

[JBoss JIRA] (TEIID-2039) Virtual table mapping with large number of UNIONs is resulting in excessively long source query

by Marc Shirley (JIRA)

Marc Shirley created TEIID-2039: ----------------------------------- Summary: Virtual table mapping with large number of UNIONs is resulting in excessively long source query Key: TEIID-2039 URL: https://issues.jboss.org/browse/TEIID-2039 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7, 7.4.1 Reporter: Marc Shirley Assignee: Steven Hawkins Queries against a virtual table built upon several layers of UNION transformations is resulting in what appears to be a badly formed, excessively long source query (for example, a SQL string over 1 million characters) that results in slow query execution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
7
0 / 0

[JBoss JIRA] (TEIID-2320) non pusable uncorrelated exists subquery will still be pushed

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2320: ------------------------------------- Summary: non pusable uncorrelated exists subquery will still be pushed Key: TEIID-2320 URL: https://issues.jboss.org/browse/TEIID-2320 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.3 The evaluation flag on the the exists predicate is not getting cloned properly, which means that an exists predicate that should be pre-evaluated (due to not being pushed-down) will instead be pushed down. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
2
0 / 0

[JBoss JIRA] (TEIID-2319) Default socket encryption for JDBC transport using mode=login is not being set in configuration file

by Van Halbert (JIRA)

Van Halbert created TEIID-2319: ---------------------------------- Summary: Default socket encryption for JDBC transport using mode=login is not being set in configuration file Key: TEIID-2319 URL: https://issues.jboss.org/browse/TEIID-2319 Project: Teiid Issue Type: Bug Components: Build/Kits Affects Versions: 8.2 Reporter: Van Halbert Assignee: Van Halbert Priority: Critical Fix For: 8.3 Referencing TEIID-2108, the login traffic should be encrypted by default. The standalone-teiid-xml does not specify <ssl mode="login" />, nor does the teiid-domain-mode-install.cli show to be adding this setting. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

4
18
0 / 0

[JBoss JIRA] (TEIID-2302) Issues setting up Teiid as an XA datasource in AS 7

by Van Halbert (JIRA)

Van Halbert created TEIID-2302: ---------------------------------- Summary: Issues setting up Teiid as an XA datasource in AS 7 Key: TEIID-2302 URL: https://issues.jboss.org/browse/TEIID-2302 Project: Teiid Issue Type: Bug Components: Build/Kits Affects Versions: 8.2 Reporter: Van Halbert Assignee: Van Halbert Priority: Minor Ran across 2 issues when trying to setup Teiid as a XA data source based on the teiid-xa-ds.zml in the jboss kit: docs/teiid/datasources/teiid/teiid-xa-ds.xml 1 - ClassNotFound for the org.hibernate.dialect.Dialect, so added: <module name="org.hibernate"/> to the teiid/client/main/module.xml 2 - seeing this error: TEIID10006 Decryption failed: java.lang.ClassNotFoundException org.teiid.client.util.ExceptionHolder from [Module "org.jboss.jts:main" but that was resolved after I changed security from: <security> <user-name>user</user-name> <password>user</password> </security> to: <xa-datasource-property name="User"> user </xa-datasource-property> <xa-datasource-property name="Password"> user </xa-datasource-property> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
6
0 / 0

[JBoss JIRA] (TEIID-2309) Add support for "conformed" tables in Teiid

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2309?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2309: --------------------------------------- There are two possibilities here from a run-time perspective. One would be to introduce the concept of a conformed schema/model. It would look like a multi-source model in that it would be a physical model with multiple sources listed. Then the user would be expected to use the conformed instance whenever Teiid is expected to choose the correct table automatically. The conformed tables could also be left in their respective schema/models so that a reference to a particular table could be forced. This first option is the least amount of work from a planner/metadata perspective. Although it's not clear how well this jives with feature requested here. This feature seems to be written as a somewhat post development activity where tables are being replicated for performance and thus references need update in existing definitions to take advantage of the now replicated table. This implies some additional Designer work. The second option would be to handle the notion of conformed at a table level. This would either be through extension metadata or an additional construct. If added as an additional metadata construct, then this is something that could be handled as a post-development activity more easily. Being able to control which source(s) a table is bound to is potentially useful beyond this feature since it give more flexibility in schema design. > Add support for "conformed" tables in Teiid > ------------------------------------------- > > Key: TEIID-2309 > URL: https://issues.jboss.org/browse/TEIID-2309 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Debbie Steigner > > Teiid would support tables from different data sources being marked as "conformed", meaning they are the same (or perhaps a different name). When optimising a query, it would take the conformity into account and choose the appropriate copy of the table (presumably one in the same database as other tables in the query, if available). I would not regard it as a problem if Teiid *required* the dimensions to be strictly the same as opposed to permitting subsets, though as with so many areas, it would be up to the user to ensure this was really true: I would not expect the engine to do anything to verify that the tables really were conformed. > Usecase: > In Data Warehousing, it is relatively common to have multiple copies of the same dimensions spread over multiple Data Warehouses or Marts, or in the same Data Warehouse when associated with different Fact Tables. If these copies are either identical or strict subsets of an idealised dimension (and, by extension, share *exactly* the same naming and structure), then they may be said to be "conformed". It is expected that the dimension includes at least the values required to support the facts in the database in which it occurs or the Fact Table to which it is paired. > Example: > > Source S1: > > BIGBIGBIG (millions of rows) > bigkey > ccy > other_stuff > > CURRENCY (100s of rows) let's call it S1_CCY if we need to distinguish > ccy > ccy_name > > > Source S2: > > BIGGER (millions of rows) > biggerkey > bigkey > ccy > more_stuff > > CURRENCY (100s of rows) similarly, S2_CCY > ccy > ccy_name > > > When executing: > > SELECT B.* > FROM BIGBIGBIG B, > CURRENCY CCY > WHERE B.ccy = CCY.ccy > AND CCY.ccy_name LIKE "%DOLLAR%" > > Then it is clearly advantageous to use the copy of CURRENCY in S1 and re-write the query using S1_CCY. In this situation, federation is eliminated completely. > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2318) Powerhub driver not working with Teiid

by Tanmoy Palit (JIRA)

Tanmoy Palit created TEIID-2318: ----------------------------------- Summary: Powerhub driver not working with Teiid Key: TEIID-2318 URL: https://issues.jboss.org/browse/TEIID-2318 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 7.7 Environment: Windows Vista 64 bit Reporter: Tanmoy Palit Assignee: Steven Hawkins Priority: Blocker Powerhub drvier which is com.lgc.dam.phs.client.jdbc.PhsJDBCDriver, is a custom JDBC driver from Landmark. Connection string looks like the following: jdbc:scwapi:<server_name>;<powerhub_user>;<passwd>;<database_instance><database_name;<username>;<dbpasswd> Getting the following error when Teiid Designer is used to consume the underlying database: Error: Unexpected exception while calling com.lgc.dam.phs.client.jdbc.PhsJDBCDatabaseMetaData.getTableTypes() and processing results on Acceptance PowerExplorer.CDSPROD Here is the complete stack trace for the error: java.lang.NullPointerException at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportMetadataPage.initializeInTransaction(JdbcImportMetadataPage.java:313) at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportMetadataPage.setVisible(JdbcImportMetadataPage.java:238) at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1260) at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1239) at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1228) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1226) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:150) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:277) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.ui.internal.actions.CommandAction.run(CommandAction.java:171) at org.eclipse.ui.actions.ImportResourcesAction.run(ImportResourcesAction.java:97) at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) Squrriel SQL Client successfully connects to metadata and executes queries to this Powerhub data source using same PhsJDBC driver -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2284) Create Teiid RHQ Plugin for Teiid8/AS7/RHQ 4.4

by Ted Jones (JIRA)

Ted Jones created TEIID-2284: -------------------------------- Summary: Create Teiid RHQ Plugin for Teiid8/AS7/RHQ 4.4 Key: TEIID-2284 URL: https://issues.jboss.org/browse/TEIID-2284 Project: Teiid Issue Type: Task Reporter: Ted Jones Assignee: Ted Jones Need to create a Teiid RHQ plugin that will support Teiid 8.x and run on RHQ 4.4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2012