[JBoss JIRA] (TEIIDDES-2231) Rename "Mapped Role Names" to "Mapped Enterprise Groups"
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIIDDES-2231:
--------------------------------------
Summary: Rename "Mapped Role Names" to "Mapped Enterprise Groups"
Key: TEIIDDES-2231
URL: https://issues.jboss.org/browse/TEIIDDES-2231
Project: Teiid Designer
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Usability
Reporter: Ramesh Reddy
Data Roles dialog box shows "Mapped Role Names" as name to map the data-roles to enterprise groups. Talking with couple people I realized that, users are not readily able to grasp two concepts of mapping data-role name with enterprise groups.
If the name is changed to "Mapped Enterprise Group" then it will little bit more clear about the intention. Also, if we can add a description like,
"One to one mapping of a enterprise group of the logged in user based on JAAS authentication on the server"
that would be informational.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2218) JBossWS-CXF/RestEasy WAR menu options are impl specific
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2218?page=com.atlassian.jira.plu... ]
Ted Jones resolved TEIIDDES-2218.
---------------------------------
Fix Version/s: 8.6
Resolution: Done
Changed SOAP and REST war generation menu options and updated documentation accordingly.
https://github.com/Teiid-Designer/teiid-designer/pull/380
> JBossWS-CXF/RestEasy WAR menu options are impl specific
> -------------------------------------------------------
>
> Key: TEIIDDES-2218
> URL: https://issues.jboss.org/browse/TEIIDDES-2218
> Project: Teiid Designer
> Issue Type: Quality Risk
> Security Level: Public(Everyone can see)
> Components: Documentation, Usability
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: 8.6, 8.5.1
>
>
> I never noticed noticed this before, but the menu options as
> - Generate JBossWs-CXF War
> - Generate RestEasy War
> they seem to mention the underlying technologies that Designer uses to implement the WAR files then generic name such as
> - Generate SOAP Web Service WAR
> - Generate REST Web Service WAR
> The users do not care, may not be aware of above underlying technologies, and can create a confusing naming.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2229) Merge various fixes from master into 8.5.1
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2229?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-2229:
--------------------------------
Description:
*Candidates*
TEIIDDES-2224 web service returns 500 when concurrent access
TEIIDDES-2218 JBossWS-CXF/RestEasy WAR menu options are impl specific
*Completed Upstream*
TEIIDDES-#### <title>
was:
*Candidates*
TEIIDDES-2224 web service returns 500 when concurrent access
*Completed Upstream*
TEIIDDES-#### <title>
> Merge various fixes from master into 8.5.1
> ------------------------------------------
>
> Key: TEIIDDES-2229
> URL: https://issues.jboss.org/browse/TEIIDDES-2229
> Project: Teiid Designer
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 8.5.1
> Reporter: Ted Jones
> Assignee: Johnathon Lee
> Priority: Blocker
> Fix For: 8.5.1
>
>
> *Candidates*
> TEIIDDES-2224 web service returns 500 when concurrent access
> TEIIDDES-2218 JBossWS-CXF/RestEasy WAR menu options are impl specific
> *Completed Upstream*
> TEIIDDES-#### <title>
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2219) Preview Issue - when non-Type4 JDBC driver is used.
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2219?page=com.atlassian.jira.plu... ]
Mark Drilling updated TEIIDDES-2219:
------------------------------------
Attachment: ojdbc14.jar
attached driver that I used.
> 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
> Security Level: Public(Everyone can see)
> Components: Data Preview
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Barry LaFond
> Fix For: 8.6
>
> 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
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2219) Preview Issue - when non-Type4 JDBC driver is used.
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2219?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2219:
--------------------------------------
Assignee: Barry LaFond (was: Mark Drilling)
> 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
> Security Level: Public(Everyone can see)
> Components: Data Preview
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Barry LaFond
> Fix For: 8.6
>
>
> 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
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2178) Teiid Connection importer by default only waits for 120 seconds for schema
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2178?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2178.
------------------------------------
Resolution: Done
Done - completed for 8.5 release
> Teiid Connection importer by default only waits for 120 seconds for schema
> --------------------------------------------------------------------------
>
> Key: TEIIDDES-2178
> URL: https://issues.jboss.org/browse/TEIIDDES-2178
> Project: Teiid Designer
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Import/Export
> Affects Versions: 8.4, 8.3.2
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Fix For: 8.5
>
>
> When using the Teiid connection importer it sends the query to the server and waits for up to 120 seconds for server to return metadata. If the server returned data it is fine, otherwise it fails.
> Some times when working with larger metadata or slower connections it may take more than 120 seconds, the UI should give user an option to terminate or wait for another +n of seconds.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2178) Teiid Connection importer by default only waits for 120 seconds for schema
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2178?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2178:
-----------------------------------
Fix Version/s: 8.5
(was: 8.6)
> Teiid Connection importer by default only waits for 120 seconds for schema
> --------------------------------------------------------------------------
>
> Key: TEIIDDES-2178
> URL: https://issues.jboss.org/browse/TEIIDDES-2178
> Project: Teiid Designer
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Import/Export
> Affects Versions: 8.4, 8.3.2
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Fix For: 8.5
>
>
> When using the Teiid connection importer it sends the query to the server and waits for up to 120 seconds for server to return metadata. If the server returned data it is fine, otherwise it fails.
> Some times when working with larger metadata or slower connections it may take more than 120 seconds, the UI should give user an option to terminate or wait for another +n of seconds.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-1657) Update and publish E2E Yahoo UDF Test Script as wiki document
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1657?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1657.
------------------------------------
Assignee: Barry LaFond
Resolution: Done
We've added a complete wiki example page that includes UDF functionality:
https://community.jboss.org/docs/DOC-52623
Marking as done
> Update and publish E2E Yahoo UDF Test Script as wiki document
> -------------------------------------------------------------
>
> Key: TEIIDDES-1657
> URL: https://issues.jboss.org/browse/TEIIDDES-1657
> Project: Teiid Designer
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Documentation
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.6
>
> Attachments: TestUDF.jar, translator-yahoo-7.1.0.jar
>
>
> The E2E Yahoo UDF Test Script involves helping users understand and work with a custom translator as well as a User Defined Function.
> Develop a Wiki article that walks a user through the setup, modeling and testing of this use-case.
> Attached is the custom translator jar and the custom UDF jar.
> Note for 8.3, the notion of UDF's are now confined to View models. See TEIIDDES-1973 and TEIIDDES-1974 for changes and tweak the E2E script to reflect these changes.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months