[JBoss JIRA] (TEIIDDES-2324) Rest Importer: Use invokeHTTP procedure with Named Parameters
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2324?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-2324:
--------------------------------
Fix Version/s: 8.7
> Rest Importer: Use invokeHTTP procedure with Named Parameters
> -------------------------------------------------------------
>
> Key: TEIIDDES-2324
> URL: https://issues.jboss.org/browse/TEIIDDES-2324
> Project: Teiid Designer
> Issue Type: Enhancement
> Affects Versions: 8.6
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: 8.7, 8.6.1
>
>
> When generating the transformation for rest procedure, in the invokeHTTP procedure, use named procedures. aka like
> invokeHTTP (action=>'GET', endpoint=>qp, stream=>'true')
> this way one can avoid putting the null parametes, as well as if there are additional parameters added to invokeHTTP as did in TEIID-3016 the generated procedure will be error free for next versions. I did see one error here with Teiid 8.9 Alpha, which is logged as TEIID-3107
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (TEIIDDES-2328) Rest Importer: Show the response document
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2328?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-2328:
--------------------------------
Fix Version/s: 8.7
> Rest Importer: Show the response document
> -----------------------------------------
>
> Key: TEIIDDES-2328
> URL: https://issues.jboss.org/browse/TEIIDDES-2328
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 8.6
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: 8.7, 8.6.1
>
> Attachments: showdocument.png
>
>
> I used the one of the REST APIs from [http://nycpulse.herokuapp.com/api]
> For this JIRA, I was using [http://mtaapi.herokuapp.com/times?hour=10&minute=25]
> The importer says the response document is bad, see the attached screen shot. The repose is like
> {code}
> {
> "result": [
> {
> "arrival": "10:25:00",
> "id": "242N",
> "lat": "40.662742",
> "lon": "-73.95085",
> "name": "Sterling St"
> },
> {
> "arrival": "10:25:00",
> "id": "242N",
> "lat": "40.662742",
> "lon": "-73.95085",
> "name": "Sterling St"
> },
> {
> "arrival": "10:25:30",
> "id": "A09S",
> "lat": "40.840719",
> "lon": "-73.939561",
> "name": "168 St"
> }
> }
> {code}
> So, that looks like valid JSON to me. So, two part question
> 1) Why importer complaining? fix any errors as such
> 2) The gist of this JIRA, instead of showing link to some response file, that I have no way to check the contents if wanted, show the response document itself. This pattern is not new, CSV importer and XML importer do show the document to user, which IMO is much more valuable and gives visual indication right away what they are working with.
> I even say this needs to be done File based importer too (create JIRA if you decide to work on this separately)
>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (TEIIDDES-2324) Rest Importer: Use invokeHTTP procedure with Named Parameters
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2324?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-2324:
--------------------------------
Fix Version/s: 8.6.1
(was: 8.6)
> Rest Importer: Use invokeHTTP procedure with Named Parameters
> -------------------------------------------------------------
>
> Key: TEIIDDES-2324
> URL: https://issues.jboss.org/browse/TEIIDDES-2324
> Project: Teiid Designer
> Issue Type: Enhancement
> Affects Versions: 8.6
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: 8.6.1
>
>
> When generating the transformation for rest procedure, in the invokeHTTP procedure, use named procedures. aka like
> invokeHTTP (action=>'GET', endpoint=>qp, stream=>'true')
> this way one can avoid putting the null parametes, as well as if there are additional parameters added to invokeHTTP as did in TEIID-3016 the generated procedure will be error free for next versions. I did see one error here with Teiid 8.9 Alpha, which is logged as TEIID-3107
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (TEIIDDES-2328) Rest Importer: Show the response document
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2328?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-2328:
--------------------------------
Fix Version/s: 8.6.1
(was: 8.6)
> Rest Importer: Show the response document
> -----------------------------------------
>
> Key: TEIIDDES-2328
> URL: https://issues.jboss.org/browse/TEIIDDES-2328
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 8.6
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: 8.6.1
>
> Attachments: showdocument.png
>
>
> I used the one of the REST APIs from [http://nycpulse.herokuapp.com/api]
> For this JIRA, I was using [http://mtaapi.herokuapp.com/times?hour=10&minute=25]
> The importer says the response document is bad, see the attached screen shot. The repose is like
> {code}
> {
> "result": [
> {
> "arrival": "10:25:00",
> "id": "242N",
> "lat": "40.662742",
> "lon": "-73.95085",
> "name": "Sterling St"
> },
> {
> "arrival": "10:25:00",
> "id": "242N",
> "lat": "40.662742",
> "lon": "-73.95085",
> "name": "Sterling St"
> },
> {
> "arrival": "10:25:30",
> "id": "A09S",
> "lat": "40.840719",
> "lon": "-73.939561",
> "name": "168 St"
> }
> }
> {code}
> So, that looks like valid JSON to me. So, two part question
> 1) Why importer complaining? fix any errors as such
> 2) The gist of this JIRA, instead of showing link to some response file, that I have no way to check the contents if wanted, show the response document itself. This pattern is not new, CSV importer and XML importer do show the document to user, which IMO is much more valuable and gives visual indication right away what they are working with.
> I even say this needs to be done File based importer too (create JIRA if you decide to work on this separately)
>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 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: Ted Jones)
> 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
> 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.3.1#6329)
11 years, 7 months
[JBoss JIRA] (TEIIDDES-2333) Use of eclipse internal classes in ControlledPopupMenuExtender
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2333?page=com.atlassian.jira.plu... ]
Paul Richardson updated TEIIDDES-2333:
--------------------------------------
Description:
Upgrading the Target Platform to Luna, the [ControllerPopupMenuExtender|https://github.com/Teiid-Designer/teiid-desig...] shows a compile error due a change in API of the contributeObjectActions() method.
Since this method is internal, it is within scope for Eclipse to change its API. In retrospect, Designer should rewrite this class to avoid the use of the internal API, which would increase the chances of transitioning, between target platforms, being much more seamless.
> Use of eclipse internal classes in ControlledPopupMenuExtender
> --------------------------------------------------------------
>
> Key: TEIIDDES-2333
> URL: https://issues.jboss.org/browse/TEIIDDES-2333
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Paul Richardson
>
> Upgrading the Target Platform to Luna, the [ControllerPopupMenuExtender|https://github.com/Teiid-Designer/teiid-desig...] shows a compile error due a change in API of the contributeObjectActions() method.
> Since this method is internal, it is within scope for Eclipse to change its API. In retrospect, Designer should rewrite this class to avoid the use of the internal API, which would increase the chances of transitioning, between target platforms, being much more seamless.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months