[JBoss JIRA] (TEIIDDES-2219) Preview Issue - when non-Type4 JDBC driver is used.
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2219?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-2219.
----------------------------------
> Preview Issue - when non-Type4 JDBC driver is used.
> ---------------------------------------------------
>
> Key: TEIIDDES-2219
> URL: https://issues.jboss.org/browse/TEIIDDES-2219
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview, Patch Release
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Attachments: ojdbc14.jar
>
>
> Encountered issue when trying to preview an Oracle source table in Designer. The preview failed with the following in the server log:
> 10:39:44,877 WARN [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue0) TEIID30020 Processing exception for request N0JYBgYp8yw2.0 'TEIID30498 Capabilities for OracleSource were not avaialable. The command could not be planned properly.'. Originally QueryPlannerException PlanToProcessConverter.java:324. Enable more detailed logging to see the entire stacktrace.
> Upon debug, I found that the 'type' for my deployed oracle driver 'ojdbc14.jar' was not found on the server. The ojdbc14.jar was actually getting deployed in ExecutionAdmin, but the type was not present - because it was not a type4 jdbc driver.
> However, the preview proceeded (and failed) with the above exception.
> We need to investigate and handle this case more gracefully in Designer. The preview should not proceed - we should catch this error and display to the user - and stop the preview attempt.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIIDDES-1618) Support partition statistics
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1618?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-1618.
----------------------------------
> Support partition statistics
> ----------------------------
>
> Key: TEIIDDES-1618
> URL: https://issues.jboss.org/browse/TEIIDDES-1618
> Project: Teiid Designer
> Issue Type: Feature Request
> Reporter: Van Halbert
> Assignee: Barry LaFond
>
> The stats gathering feature does not take into account of partition statistics. Most of our query hit a single partition and using the global stats is not a true indication of the statistics for the single partition. It would be nice if Teiid engine can differentiate the usage of global and partition statistics during the optimisation and planning stages.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIIDDES-2268) NPE An internal error occurred during: "Loading Core provider".
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2268?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-2268.
----------------------------------
> NPE An internal error occurred during: "Loading Core provider".
> ---------------------------------------------------------------
>
> Key: TEIIDDES-2268
> URL: https://issues.jboss.org/browse/TEIIDDES-2268
> Project: Teiid Designer
> Issue Type: Bug
> Components: Datatools Integration
> Affects Versions: 8.5, 8.6
> Environment: windows 7, eclipse kepler 4.3.2, teiid designer 8.5/8.6
> Reporter: Greg MacKinnon
> Assignee: Paul Richardson
>
> Here is a representative stack trace. This had been observed in teiid designer 8.5. I fetched the 8.6 teiid designer code, built and installed in on eclipse to workaround an AuthenticationType issue and have observed this NPE there as well.
>
> !ENTRY org.eclipse.core.jobs 4 2 2014-07-24 15:34:22.685
> !MESSAGE An internal error occurred during: "Loading Core provider".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.datatools.connectivity.sqm.internal.core.definition.isAuthorizationIdentifierSupported(DatabaseDefinitionImpl.java:2014)
> at org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.layout.vnode.ServerExplorerVNodeContentProviderNav.displayDatabaseChildren(ServerExplorerVNodeContentProviderNav.java:391)
> at org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.layout.AbstractOnDemandContentProviderNav.getChildren(AbstractOnDemandContentProviderNav.java:116)
> at org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.layout.AbstractOnDemandContentProviderNav.getChildren(AbstractOnDemandContentProviderNav.java:239)
> at org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.layout.AbstractLayoutProviderNav.getChildren(AbstractLayoutProviderNav.java:85)
> at org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.impl.ServerExplorerContentProviderNav.load(ServerExplorerContentProviderNav.java:153)
> at org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.loading.LoadingJob.run(LoadingJob.java:43)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
>
> This occurs right after a call is made to load the definition.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months