[JBoss JIRA] (TEIID-2757) XML reserved characters not support in Odata
by Patrick Deenen (JIRA)
[ https://issues.jboss.org/browse/TEIID-2757?page=com.atlassian.jira.plugin... ]
Patrick Deenen commented on TEIID-2757:
---------------------------------------
Hi Steven,
I reopened the customer support case.
I would prefer the 'invalid character replacement in Teiid' as a solution. I don's the other alternatives as workable options.
Thx,
Patrick
> XML reserved characters not support in Odata
> --------------------------------------------
>
> Key: TEIID-2757
> URL: https://issues.jboss.org/browse/TEIID-2757
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.4
> Environment: EAP version 6.1 with Teiid 8.5
> Reporter: Marc Shirley
> Assignee: Steven Hawkins
> Attachments: TEIID-2757-Webservices-Stacktrace.txt
>
>
> The odata framework sometimes has problems with transforming characters (reserved in XML) from the source data to the XML result. The result is an exception: TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: com.ctc.wstx.exc.WstxIOException: Invalid white space character (0x1b) in text to output (in xml 1.1, could output as a character entity).
--
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
11 years, 1 month
[JBoss JIRA] (TEIID-2730) Cannot query Sybase database with jconn3.jar
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2730?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-2730:
------------------------------------------------
belong(a)redhat.com changed the Status of [bug 1028380|https://bugzilla.redhat.com/show_bug.cgi?id=1028380] from ASSIGNED to NEW
> Cannot query Sybase database with jconn3.jar
> --------------------------------------------
>
> Key: TEIID-2730
> URL: https://issues.jboss.org/browse/TEIID-2730
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.4
> Environment: java oracle 1.7, Teiid 8.4.1-redhat4 in DV 6.0.0.ER3, Teiid Designer 8.3.beta3
> Reporter: Lucie Fabrikova
> Assignee: Steven Hawkins
> Fix For: 8.6
>
> Attachments: bqtHNB.vdb, bqt_HNB.xmi, jconn3.jar
>
>
> In teiid designer, I created a connection profile to Sybase database with URL jdbc:sybase:Tds:vmg07.mw.lab.eng.bos.redhat.com:5000/bqt2 and driver jconn3.jar.
> I created a relational source model from the jdbc connection and VDB with the source model. Then I deployed the VDB and executed query select * from "bqt_HNB"."g1" which resulted in this error message:
> TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 bqt_HNB: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]
> Console:
> OPTIMIZATION COMPLETE:
> PROCESSOR PLAN:
> AccessNode(0) output=[bqt_HNB.g1.e1, bqt_HNB.g1.e2] SELECT g_0.e1, g_0.e2 FROM bqt_HNB.g1 AS g_0
> ============================================================================
> 10:55:07,362 INFO [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) SybaseExecutionFactory Commit=true;DatabaseProductName=Adaptive Server Enterprise;DatabaseProductVersion=Adaptive Server Enterprise/15.0.3/EBF 16549 ESD#1/P/x86_64/Enterprise Linux/ase1503/2681/64-bit/FBO/Mon Mar 9 04:10:47 2009;DriverMajorVersion=6;DriverMajorVersion=0;DriverName=jConnect (TM) for JDBC (TM);DriverVersion=jConnect (TM) for JDBC(TM)/6.05(Build 26564)/P/EBF16903/JDK14/Sun May 31 1:05:35 2009;IsolationLevel=2
> 10:55:07,555 WARN [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) Connector worker process failed for atomic-request=dg2FpIhALlUI.0.0.0: org.teiid.translator.jdbc.JDBCExecutionException: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:88)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:254) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:444) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:157) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:154) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_45]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_45]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]
> Caused by: com.sybase.jdbc3.jdbc.SybSQLException: Incorrect syntax near 'e1'.
> at com.sybase.jdbc3.tds.Tds.a(Unknown Source)
> at com.sybase.jdbc3.tds.Tds.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.queryLoop(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.executeQuery(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybPreparedStatement.executeQuery(Unknown Source)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:84)
> ... 13 more
> 10:55:07,568 WARN [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2) TEIID30020 Processing exception for request dg2FpIhALlUI.0 'TEIID30504 bqt_HNB: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]'. Originally TeiidProcessingException 'Incorrect syntax near 'e1'.
> ' com.sybase.jdbc3.tds.Tds.a(Unknown Source). Enable more detailed logging to see the entire stacktrace.
--
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
11 years, 1 month
[JBoss JIRA] (TEIID-2760) Add direct query support to SimpleDB
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2760:
-------------------------------------
Summary: Add direct query support to SimpleDB
Key: TEIID-2760
URL: https://issues.jboss.org/browse/TEIID-2760
Project: Teiid
Issue Type: Enhancement
Components: Misc. Connectors
Affects Versions: 8.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.7
The direct query procedure and the native-query support for views/procedures should be added to the new SimpleDB translator.
--
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
11 years, 1 month
[JBoss JIRA] (TEIID-2759) Unable to import SAP NW-Gateway OData using sap-nw-gateway translator
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2759?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-2759.
---------------------------------
Labels: Alpha1 (was: )
Assignee: Ramesh Reddy (was: Mark Drilling)
Fix Version/s: 8.4.1
8.7
Resolution: Done
Opted to override the error parser that is not generating a valid XML (was generating with multiple roots if inner error is defined such with outer element)
The parser generates with inner error with a root element. Thus fixes the issue.
> Unable to import SAP NW-Gateway OData using sap-nw-gateway translator
> ----------------------------------------------------------------------
>
> Key: TEIID-2759
> URL: https://issues.jboss.org/browse/TEIID-2759
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.4.1
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Labels: Alpha1
> Fix For: 8.4.1, 8.7
>
> Attachments: ODataVDB.vdb, SAPGateway.ddl
>
>
> "No difference report was found" Error
> I am trying to test SAP NW-GATEWAY OData with DV6-ER4 and JDBS 7.0.1.GA/Designer 8.3.0-CR1
> The following steps will reproduce the error:
> 1. Do an import/Designer/Teiid Connection >> Source Model
> 2. Create a new datasource using webservice from available drivers
> 3. Enter Data Source Properties (can connect to the url in a browser):
> URL: https://sapes1.sapdevcenter.com/sap/opu/odata/IWFND/RMTSAMPLEFLIGHT/
> WebService Security Used: HTTPBasic
> class-name: used prefilled default
> Authentication User Name: P1940027560
> Authentication User Password: Foxrun1004
> 4. Selected the newly created driver and selected "Next"
> 5. Selected sap-nw-gateway translator and named the target model and selected "Next"
> 6. Was presented with a DDL screen and selected "Next"
> 7. The "Select the Differences to Apply" screen shows an Import Message "Error
> encountered while importing the DDL - No difference report was found". screenshot attached.
> java.lang.reflect.InvocationTargetException
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:421)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
> at org.teiid.designer.ddl.importer.ui.DdlImportDifferencesPage.setVisible(DdlImportDifferencesPage.java:217)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1259)
> at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1238)
> at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1227)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1225)
> 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:628)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:152)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
> 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:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: java.lang.NullPointerException
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.getColumnNode(CreateTableParser.java:120)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseReferenceList(CreateTableParser.java:333)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseTableBodyConstraint(CreateTableParser.java:455)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseTableBody(CreateTableParser.java:365)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parse(CreateTableParser.java:198)
> at org.modeshape.sequencer.ddl.dialect.teiid.TeiidDdlParser.parseNextStatement(TeiidDdlParser.java:150)
> at org.modeshape.sequencer.ddl.StandardDdlParser.parse(StandardDdlParser.java:209)
> at org.modeshape.sequencer.ddl.DdlParsers.parseUsing(DdlParsers.java:174)
> at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:134)
> at org.teiid.designer.ddl.importer.DdlImporter$1.tryToDo(DdlImporter.java:106)
> at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:40)
> at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:90)
> at org.teiid.designer.ddl.importer.ui.DdlImportDifferencesPage$1.run(DdlImportDifferencesPage.java:222)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> Root exception:
> java.lang.NullPointerException
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.getColumnNode(CreateTableParser.java:120)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseReferenceList(CreateTableParser.java:333)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseTableBodyConstraint(CreateTableParser.java:455)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseTableBody(CreateTableParser.java:365)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parse(CreateTableParser.java:198)
> at org.modeshape.sequencer.ddl.dialect.teiid.TeiidDdlParser.parseNextStatement(TeiidDdlParser.java:150)
> at org.modeshape.sequencer.ddl.StandardDdlParser.parse(StandardDdlParser.java:209)
> at org.modeshape.sequencer.ddl.DdlParsers.parseUsing(DdlParsers.java:174)
> at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:134)
> at org.teiid.designer.ddl.importer.DdlImporter$1.tryToDo(DdlImporter.java:106)
> at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:40)
> at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:90)
> at org.teiid.designer.ddl.importer.ui.DdlImportDifferencesPage$1.run(DdlImportDifferencesPage.java:222)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
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
11 years, 1 month
[JBoss JIRA] (TEIID-2650) A jboss server in domain mode does not advertise its teiid runtime-version
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2650?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2650.
---------------------------------
> A jboss server in domain mode does not advertise its teiid runtime-version
> --------------------------------------------------------------------------
>
> Key: TEIID-2650
> URL: https://issues.jboss.org/browse/TEIID-2650
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.4
> Reporter: Paul Richardson
> Assignee: Ramesh Reddy
> Priority: Blocker
> Fix For: 8.4.1, 8.5
>
>
> A standalone jboss server installed with teiid advertises its teiid runtime version at the path /subsystem=teiid/runtime-version.
> Likewise, a domain jboss server installed with teiid in the 'ha' profile should advertise its runtime version at the path /profile=ha/subsystem=teiid/runtime-version.
> However, whereas the standalone returns the correct value for this attribute, the domain mode server fails, only returning 'undefined'.
> This attribute is essential to designer in determining what version is the teiid instance. This in turns determines the functionality of the modelling that is available and which teiid client should be used for connection.
--
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
11 years, 1 month
[JBoss JIRA] (TEIID-2722) Cassandra: ORDER BY should do it in memory instead of trying to push down Cassandra in some cases
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2722?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2722.
---------------------------------
> Cassandra: ORDER BY should do it in memory instead of trying to push down Cassandra in some cases
> --------------------------------------------------------------------------------------------------
>
> Key: TEIID-2722
> URL: https://issues.jboss.org/browse/TEIID-2722
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: Teiid 8.6 Alpha with Cassandra 1.2.11
> Reporter: Ivan Chan
> Assignee: Ramesh Reddy
> Labels: Beta2
> Fix For: 8.6
>
>
> When I tried to join 2 tables together from same keyspace using Teiid 8.6 Alpha with Cassandra 1.2.11. It broke down SQL into 2 CQLs. However, teiid SQL transformer adds order by clause to the CQL which is not supported.
> Original SQL:
> select "cassandraDS_users"."user_id" as "cassandraDS_users_user_id",
> "cassandraDS_invoice"."sale" as "cassandraDS_invoice_sale"
> from "cassandraDS"."invoice" "cassandraDS_invoice"
> inner join "cassandraDS"."users" "cassandraDS_users" on ("cassandraDS_invoice"."user_id" = "cassandraDS_users"."user_id")
> Break Down CQL:
> SELECT cassandraDS.invoice.user_id, cassandraDS.invoice.sale FROM cassandraDS.i
> nvoice ORDER BY cassandraDS.invoice.user_id
> SELECT cassandraDS.users.user_id FROM cassandraDS.users ORDER BY cassandraDS.us
> ers.user_id
> Error from CQL Driver:
> com.datastax.driver.core.exceptions.InvalidQueryException: ORDER BY is only supported when the partition key is restricted by an EQ or an IN.
--
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
11 years, 1 month
[JBoss JIRA] (TEIID-2721) Resolving an aliased view prevents inherent update from working
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2721?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2721.
---------------------------------
> Resolving an aliased view prevents inherent update from working
> ---------------------------------------------------------------
>
> Key: TEIID-2721
> URL: https://issues.jboss.org/browse/TEIID-2721
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 8.4.1, 8.6, 7.7.9
>
> Attachments: 2721-77x.patch
>
>
> If an aliased form of an inherently updatable view is resolved first, we will cache invalid update info which prevents inherent insert/update from functioning correctly.
> For example with the view gx, first running:
> select * from gx as x
>
> will prevent an inherent insert such as:
> insert into gx (e1, e2, e3, e4) select * from pm1.g1
> from working as expected
--
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
11 years, 1 month