[JBoss JIRA] (TEIID-2600) IllegalArgumentException when creating datasource from an imported Webservice source model
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2600?page=com.atlassian.jira.plugin... ]
Steven Hawkins moved TEIIDDES-1800 to TEIID-2600:
-------------------------------------------------
Project: Teiid (was: Teiid Designer)
Key: TEIID-2600 (was: TEIIDDES-1800)
Affects Version/s: 8.0
(was: 8.2)
Component/s: AdminApi
(was: Teiid Integration)
> IllegalArgumentException when creating datasource from an imported Webservice source model
> ------------------------------------------------------------------------------------------
>
> Key: TEIID-2600
> URL: https://issues.jboss.org/browse/TEIID-2600
> Project: Teiid
> Issue Type: Bug
> Components: AdminApi
> Affects Versions: 8.0
> Reporter: Van Halbert
> Assignee: Barry LaFond
>
> After importing from a remote web service and creating the source and view models, tried to (right click on source model) create data source on teiid server (EAP 6.1 / Teiid 8.4.1) and had this issue:
> !ENTRY org.teiid.designer.dqp.ui 4 0 2013-07-25 16:59:24.847
> !MESSAGE Error creating data source for model CustomerRESTWebSvcSource.xmi
> !STACK 0
> java.lang.IllegalArgumentException: The argument value is not specified for value: ''
> at org.jboss.as.cli.operation.impl.DefaultOperationRequestBuilder.addProperty(DefaultOperationRequestBuilder.java:113)
> at org.teiid.adminapi.AdminFactory$AdminImpl.cliCall(AdminFactory.java:1397)
> at org.teiid.adminapi.AdminFactory$AdminImpl.addConfigProperty(AdminFactory.java:308)
> at org.teiid.adminapi.AdminFactory$AdminImpl.createConnectionFactory(AdminFactory.java:297)
> at org.teiid.adminapi.AdminFactory$AdminImpl.createDataSource(AdminFactory.java:412)
> at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:324)
> at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:551)
> at org.teiid.designer.runtime.ui.connection.CreateDataSourceAction.run(CreateDataSourceAction.java:156)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> 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.Display.sendEvent(Display.java:4166)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651)
> 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:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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)
--
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, 5 months
[JBoss JIRA] (TEIID-2599) Getting NPE when making a REST call
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2599?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2599:
----------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> Getting NPE when making a REST call
> -----------------------------------
>
> Key: TEIID-2599
> URL: https://issues.jboss.org/browse/TEIID-2599
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.4.1
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
>
> Making a REST call and getting the following NPE:
> 11:04:20,159 SEVERE [org.teiid.rest] (http-/127.0.0.1:8080-1) Exception in execute: {0}: java.lang.Throwable: java.lang.NullPointerException
> at org.teiid.rest.services.TeiidRSProviderPost.execute(TeiidRSProviderPost.java:134) [classes:]
> at org.teiid.rest.services.CustomerRESTWebSvcView.restProcedure(CustomerRESTWebSvcView.java:73) [classes:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_13]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_13]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_13]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_13]
--
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, 5 months
[JBoss JIRA] (TEIID-2599) Getting NPE when making a REST call
by Van Halbert (JIRA)
Van Halbert created TEIID-2599:
----------------------------------
Summary: Getting NPE when making a REST call
Key: TEIID-2599
URL: https://issues.jboss.org/browse/TEIID-2599
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.4.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Making a REST call and getting the following NPE:
11:04:20,159 SEVERE [org.teiid.rest] (http-/127.0.0.1:8080-1) Exception in execute: {0}: java.lang.Throwable: java.lang.NullPointerException
at org.teiid.rest.services.TeiidRSProviderPost.execute(TeiidRSProviderPost.java:134) [classes:]
at org.teiid.rest.services.CustomerRESTWebSvcView.restProcedure(CustomerRESTWebSvcView.java:73) [classes:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_13]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_13]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_13]
at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_13]
--
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, 5 months
[JBoss JIRA] (TEIID-2443) Support Language feature for "With Rollup"
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2443?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2443.
-----------------------------------
Labels: analytical olap (was: analytical olap teiid)
Resolution: Done
Added support for a single rollup and marked appropriate support for mysql, oracle, sqlserver, derby, etc. We may need to update the sybase translator logic to differentiate between ASE and the other sybase products.
As this feature is picked up we can look at expanded to the more general form of olap grouping (for now the single rollup ala sql server 2005/mysql/derby seems sufficient) and adding aggregate decomposition over join/union support which is simply disabled at this point.
> Support Language feature for "With Rollup"
> ------------------------------------------
>
> Key: TEIID-2443
> URL: https://issues.jboss.org/browse/TEIID-2443
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Labels: analytical, olap
> Fix For: 8.5
>
>
> It would be useful to provide the clause 'WITH ROLLUP' in Teiid for analytical type queries. Example:
> {code}
> Group Name SalesYTD
> North America Northwest 123237.00
> North America Northwest 37534.00
> North America Northwest 48003.00
> North America Southwest 164232.00
> North America Southeast 39667.00
> North America Southeast 105810.00
> Europe France 74569.00
> Europe Germany 59456.00
> Pacific Australia 93403.00
> Europe United Kingdom 78327.00
> {code}
> With query like
> {code:SQL}
> SELECT [Group], [Name], SUM([SalesYTD]) AS 'Total Sales'
> FROM Table
> GROUP BY [Group], [Name] WITH ROLLUP
> {code}
> will produce
> {code}
> Group Name Total Sales
> Europe France 74569.00
> Europe Germany 59456.00
> Europe United Kingdom 78327.00
> Europe NULL 212352.00
> North America Northwest 208774.00
> North America Southeast 145477.00
> North America Southwest 164232.00
> North America NULL 518483.00
> Pacific Australia 93403.00
> Pacific NULL 93403.00
> NULL NULL 824238.00
> {code}
> 4 rows have been added, 3 for sub total of each [Group], and 1 row for grand total.
> Teiid needa to build it's analytical function library to be useful in reporting situations.
--
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, 5 months
[JBoss JIRA] (TEIID-2583) Add support for proxy authentication
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2583?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2583:
-------------------------------------
I believe this request was written wrong to begin with.
What user is really looking for is to do proxy authentication on the connection to the data sources that Teiid talks to based on the authenticated subject, similar to reauth at data source level. See https://issues.jboss.org/browse/JBJCA-516 for re-auth support, it should be easy to write needed plugins for required JDBC drivers if they support proxy/re-auth configurations. The one thing I see limiting is, the re-auth plugin interface does not have signature to pass in the Subject in transit, just simple user name and password, that could be overly simple, when dealing with complex logins such as kerberos or custom tokens. Hopefully Subject can be retrieved from thread context, but requires a test to verify it.
The resolution on this still stands as indicated.
> Add support for proxy authentication
> ------------------------------------
>
> Key: TEIID-2583
> URL: https://issues.jboss.org/browse/TEIID-2583
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.4
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> Add support for proxy authentication. This feature was derived from Oracle's feature: http://www.oracle.com/technetwork/middleware/ias/how-to-ds-proxy-088621.h...
--
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, 5 months
[JBoss JIRA] (TEIID-2311) Add simple row based security to data roles
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2311?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2311:
-------------------------------------
See https://docs.jboss.org/author/display/TEIID/XML+Definition if you are working with Dynamic VDBs.
Also, tooling support for this feature is available from 8.2 Alpha2 version or greater. Just go the VDB explorer window, where you define the data roles, and you will be able to define the conditions too in there.
> Add simple row based security to data roles
> -------------------------------------------
>
> Key: TEIID-2311
> URL: https://issues.jboss.org/browse/TEIID-2311
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 8.2
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.3
>
>
> A common request is to implement row based security. The common workaround of modifying transformations is generally not a good solution.
> We should look at adding support for simple table filters and column masks.
> To be effective, filtering permissions however would have to act differently than normal data roles. They would need to be applied all the time - and not just against the end user queries.
> For example, for tables:
> <permission>
> <resource-name>SCHEMA.TABLE</resource-name>
> <filter>COLUMNA=2</filter>
> </permission>
> Meaning allow the CRUD of the given row only if COLUMNA has the value of 2. Any valid predicate against just the referenced table would be allowed as a filter. Each such permission would be applied as an additional predicate any time the table is referenced (in views, inserts, updates, deletes, etc.).
> Allows would not be specified here as we want the filter to always specify inclusion. Any applicable permissions in additional roles would be applied disjunctively - filter OR filter.
> We could possibly support column masks via case expressions, such as:
> <permission>
> <resource-name>SCHEMA.TABLE.COLUMN</resource-name>
> <mask>CASE WHEN ...</mask>
> </permission>
> However this is slightly more complicated. Presumably the mask would only apply to projection and makes more sense to be applied at the final output/user query (more like a data role).
> If we work the issue to specify the object type of a permission, then the name could alternatively refer to datatype or even an extension property to make the masking a little easier.
--
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, 5 months
[JBoss JIRA] (TEIID-2443) Support Language feature for "With Rollup"
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2443?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2443:
---------------------------------------
It is straight-forward for us to add support for grouping by a single rollup element:
group by rollup(col1, col2 ...)
which is the standard syntax ("WITH ROLLUP" is an older style syntax). The spec also allows for cube, grouping sets, and the ability to intermix the grouping elements - group by col1, rollup(col2 ...)
with the exception of allowing just a single cube grouping element that additional work requires a great deal more logic. It still seems worth while though to specifically add rollup support with pushdown to mysql, sql server, etc.
> Support Language feature for "With Rollup"
> ------------------------------------------
>
> Key: TEIID-2443
> URL: https://issues.jboss.org/browse/TEIID-2443
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Labels: analytical, olap, teiid
> Fix For: 8.5
>
>
> It would be useful to provide the clause 'WITH ROLLUP' in Teiid for analytical type queries. Example:
> {code}
> Group Name SalesYTD
> North America Northwest 123237.00
> North America Northwest 37534.00
> North America Northwest 48003.00
> North America Southwest 164232.00
> North America Southeast 39667.00
> North America Southeast 105810.00
> Europe France 74569.00
> Europe Germany 59456.00
> Pacific Australia 93403.00
> Europe United Kingdom 78327.00
> {code}
> With query like
> {code:SQL}
> SELECT [Group], [Name], SUM([SalesYTD]) AS 'Total Sales'
> FROM Table
> GROUP BY [Group], [Name] WITH ROLLUP
> {code}
> will produce
> {code}
> Group Name Total Sales
> Europe France 74569.00
> Europe Germany 59456.00
> Europe United Kingdom 78327.00
> Europe NULL 212352.00
> North America Northwest 208774.00
> North America Southeast 145477.00
> North America Southwest 164232.00
> North America NULL 518483.00
> Pacific Australia 93403.00
> Pacific NULL 93403.00
> NULL NULL 824238.00
> {code}
> 4 rows have been added, 3 for sub total of each [Group], and 1 row for grand total.
> Teiid needa to build it's analytical function library to be useful in reporting situations.
--
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, 5 months
[JBoss JIRA] (TEIID-2443) Support Language feature for "With Rollup"
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2443?page=com.atlassian.jira.plugin... ]
Work on TEIID-2443 started by Steven Hawkins.
> Support Language feature for "With Rollup"
> ------------------------------------------
>
> Key: TEIID-2443
> URL: https://issues.jboss.org/browse/TEIID-2443
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Labels: analytical, olap, teiid
> Fix For: 8.5
>
>
> It would be useful to provide the clause 'WITH ROLLUP' in Teiid for analytical type queries. Example:
> {code}
> Group Name SalesYTD
> North America Northwest 123237.00
> North America Northwest 37534.00
> North America Northwest 48003.00
> North America Southwest 164232.00
> North America Southeast 39667.00
> North America Southeast 105810.00
> Europe France 74569.00
> Europe Germany 59456.00
> Pacific Australia 93403.00
> Europe United Kingdom 78327.00
> {code}
> With query like
> {code:SQL}
> SELECT [Group], [Name], SUM([SalesYTD]) AS 'Total Sales'
> FROM Table
> GROUP BY [Group], [Name] WITH ROLLUP
> {code}
> will produce
> {code}
> Group Name Total Sales
> Europe France 74569.00
> Europe Germany 59456.00
> Europe United Kingdom 78327.00
> Europe NULL 212352.00
> North America Northwest 208774.00
> North America Southeast 145477.00
> North America Southwest 164232.00
> North America NULL 518483.00
> Pacific Australia 93403.00
> Pacific NULL 93403.00
> NULL NULL 824238.00
> {code}
> 4 rows have been added, 3 for sub total of each [Group], and 1 row for grand total.
> Teiid needa to build it's analytical function library to be useful in reporting situations.
--
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, 5 months
[JBoss JIRA] (TEIID-2311) Add simple row based security to data roles
by Xian Liu (JIRA)
[ https://issues.jboss.org/browse/TEIID-2311?page=com.atlassian.jira.plugin... ]
Xian Liu commented on TEIID-2311:
---------------------------------
just one question,how to use sql in the permission condition,can be more detailed?
> Add simple row based security to data roles
> -------------------------------------------
>
> Key: TEIID-2311
> URL: https://issues.jboss.org/browse/TEIID-2311
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 8.2
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.3
>
>
> A common request is to implement row based security. The common workaround of modifying transformations is generally not a good solution.
> We should look at adding support for simple table filters and column masks.
> To be effective, filtering permissions however would have to act differently than normal data roles. They would need to be applied all the time - and not just against the end user queries.
> For example, for tables:
> <permission>
> <resource-name>SCHEMA.TABLE</resource-name>
> <filter>COLUMNA=2</filter>
> </permission>
> Meaning allow the CRUD of the given row only if COLUMNA has the value of 2. Any valid predicate against just the referenced table would be allowed as a filter. Each such permission would be applied as an additional predicate any time the table is referenced (in views, inserts, updates, deletes, etc.).
> Allows would not be specified here as we want the filter to always specify inclusion. Any applicable permissions in additional roles would be applied disjunctively - filter OR filter.
> We could possibly support column masks via case expressions, such as:
> <permission>
> <resource-name>SCHEMA.TABLE.COLUMN</resource-name>
> <mask>CASE WHEN ...</mask>
> </permission>
> However this is slightly more complicated. Presumably the mask would only apply to projection and makes more sense to be applied at the final output/user query (more like a data role).
> If we work the issue to specify the object type of a permission, then the name could alternatively refer to datatype or even an extension property to make the masking a little easier.
--
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, 5 months