[JBoss JIRA] Moved: (TEIIDDES-331) SalesForce importer's Native Type value for columns causes problems when tables are materialized.
by Van Halbert (JIRA)
[ https://jira.jboss.org/jira/browse/TEIIDDES-331?page=com.atlassian.jira.p... ]
Van Halbert moved JBEDSP-1172 to TEIIDDES-331:
----------------------------------------------
Project: Teiid Designer (was: JBoss Enterprise Data Services Platform)
Key: TEIIDDES-331 (was: JBEDSP-1172)
Component/s: Import/Export
(was: Designer)
Affects Version/s: (was: 5.5.2)
> SalesForce importer's Native Type value for columns causes problems when tables are materialized.
> -------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-331
> URL: https://jira.jboss.org/jira/browse/TEIIDDES-331
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Environment: Windows 2003 Server, 5.5.2 MMX with SFDC Technical Preview Release installed
> Reporter: Michael Walker
> Priority: Minor
>
> The SFDC importer uses the Native Type field of each column to represent the native type in SFDC. These types can include "picklist", "currency", and other SFDC-specific types. The importer correctly maps these native types to the appropriate Java type, e.g. "string", "double", etc.
> Views built off imported SFDC objects will also contain this native type information.
> If these views are materialized, our materialized views script generation will use whatever Native Type setting is found in the view. This ends up generating table creation scripts that uses types that have no meaning in the source system (see attached example).
> If we continue to use materialized views script generation, we should take care not to use invalid native type values, but instead, convert the Java type back to the appropriate SQL type for the source system.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Moved: (TEIIDDES-329) Operations Editor does not correctly wrap user-entered SQL with CREATE... and END
by Van Halbert (JIRA)
[ https://jira.jboss.org/jira/browse/TEIIDDES-329?page=com.atlassian.jira.p... ]
Van Halbert moved JBEDSP-1115 to TEIIDDES-329:
----------------------------------------------
Project: Teiid Designer (was: JBoss Enterprise Data Services Platform)
Key: TEIIDDES-329 (was: JBEDSP-1115)
Component/s: (was: Designer)
Affects Version/s: (was: 5.5.4)
> Operations Editor does not correctly wrap user-entered SQL with CREATE... and END
> ---------------------------------------------------------------------------------
>
> Key: TEIIDDES-329
> URL: https://jira.jboss.org/jira/browse/TEIIDDES-329
> Project: Teiid Designer
> Issue Type: Bug
> Environment: fedora 10, Designer build 3257
> Reporter: Paul Nittel
>
> I ran across this while running the E2E Updateable Web Service Test Script.
> After creating the Web Service interface and initial steps of creating the InsertProduct operation, I pasted in the SQL. When I validated the SQL, the Designer wrapped it, beginning with the CREATE, and ending with END. Unfortunately, the terminating END is placed immedately after the END in the pasted in text. The validation then fails when it reaches the new word, "ENDEND". (the user needs to separate the "ENDEND" into "END END" and it will parse correctly.
> The error message is:
> The query is not parsable.
> Parsing error: Encountered "<EOF>" at line 1, column 464.
> Was expecting:
> "=" ...
> The SQL winds up being:
> CREATE VIRTUAL PROCEDURE BEGIN DECLARE string VARIABLES.IN_ID = xpathvalue(ProductsWebSvc.ProdInterface.DeleteProduct.ProductIdIn, '/*:InstrIdInput/*:ID'); DECLARE integer VARIABLES.delete_count = 0; VARIABLES.DELETE_COUNT = DELETE FROM Updates.UpdateProduct WHERE Updates.UpdateProduct.INSTR_ID = VARIABLES.IN_ID; IF(VARIABLES.DELETE_COUNT = 1) BEGIN SELECT * FROM ProductDoc.goodResultsDocument; END ELSE BEGIN SELECT * FROM ProductDoc.badResultsDocument; ENDEND
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Moved: (TEIIDDES-328) Maximum Result Rows default is unlimited in Designer, 10, 000 in Console
by Van Halbert (JIRA)
[ https://jira.jboss.org/jira/browse/TEIIDDES-328?page=com.atlassian.jira.p... ]
Van Halbert moved JBEDSP-1171 to TEIIDDES-328:
----------------------------------------------
Project: Teiid Designer (was: JBoss Enterprise Data Services Platform)
Key: TEIIDDES-328 (was: JBEDSP-1171)
Component/s: (was: Designer)
(was: Console)
Affects Version/s: (was: 5.5.4)
> Maximum Result Rows default is unlimited in Designer, 10,000 in Console
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-328
> URL: https://jira.jboss.org/jira/browse/TEIIDDES-328
> Project: Teiid Designer
> Issue Type: Bug
> Environment: Fedora 10, build 3237
> Reporter: Paul Nittel
>
> I ran the TPCR test which specifies setting the Maximum result Rows property to 7,000,000. The connector binding the Designer created showed blanks for the Max. When I ran the queries, they all passed. When I deployed the VDB to the Console, Maximum Result Rows was the old default of 10,000.
> They should be the same, IMHO. Or, I'd make the Designer default 10,000 and the Console's unlimited.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Moved: (TEIIDDES-326) Excessive error reporting when virtual model's sources are removed (UUIDs, for example)
by Van Halbert (JIRA)
[ https://jira.jboss.org/jira/browse/TEIIDDES-326?page=com.atlassian.jira.p... ]
Van Halbert moved JBEDSP-971 to TEIIDDES-326:
---------------------------------------------
Project: Teiid Designer (was: JBoss Enterprise Data Services Platform)
Key: TEIIDDES-326 (was: JBEDSP-971)
Component/s: (was: Designer)
Affects Version/s: (was: 5.5.3)
> Excessive error reporting when virtual model's sources are removed (UUIDs, for example)
> ---------------------------------------------------------------------------------------
>
> Key: TEIIDDES-326
> URL: https://jira.jboss.org/jira/browse/TEIIDDES-326
> Project: Teiid Designer
> Issue Type: Bug
> Environment: Fedora 10
> Reporter: Paul Nittel
> Assignee: Barry LaFond
>
> This was suggested by Dan. (Blame him, not me:-)
> Create a project
> Create a physical model with a couple of columns
> Create a virtual model, transforming from the physical
> Save everything
> (at this point there should be no warnings or errors in Problems)
> Delete the physical model (click all applicable OKs)
> I now have 5 errors:
> 1 - Sql transformation in the model vFizz contains the unresolved reference file:/home/pnittel/mmx/553ga/des/workspace/deletoid/Fizz.xmi#mmuuid/2a434440-3dcd-1124-891d-8961aeed3f64
> 2 - Sql transformation in the model vFizz contains the unresolved reference file:/home/pnittel/mmx/553ga/des/workspace/deletoid/Fizz.xmi#mmuuid/315c0f80-3dcf-1124-891d-8961aeed3f64
> 3 - Unresolved reference "file:/home/pnittel/mmx/553ga/des/workspace/deletoid/Fizz.xmi"
> 4 - Group does not exist: mmuuid:6c984d80-3dc9-1124-891d-8961aeed3f64
> 5 - Unable to resolve the imported model Fizz.xmi
> Errors 1, 2, and 4 reference UUIDs and are, therefore, pretty useless to a user. Errors 3 and 4 are more useful. Can we get rid of the excessively "geeky" UUID references in these messages?
> It also generates an entry in the Message Log:
> Error 2009-02-20 13:37:29.431 Unable to resolve reference to a resource with the URI file:/home/pnittel/mmx/553ga/des/workspace/deletoid/Fizz.xmi
> IMHO, I don't think a validation error should be in the message log.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Moved: (TEIIDDES-325) Web Service As Relational importer cannot handle web services that have an input but no output
by Van Halbert (JIRA)
[ https://jira.jboss.org/jira/browse/TEIIDDES-325?page=com.atlassian.jira.p... ]
Van Halbert moved JBEDSP-851 to TEIIDDES-325:
---------------------------------------------
Project: Teiid Designer (was: JBoss Enterprise Data Services Platform)
Key: TEIIDDES-325 (was: JBEDSP-851)
Component/s: Import/Export
(was: Designer)
Affects Version/s: (was: 5.5.3)
> Web Service As Relational importer cannot handle web services that have an input but no output
> ----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-325
> URL: https://jira.jboss.org/jira/browse/TEIIDDES-325
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Environment: 5.5SP3 GA Designer on Linux
> Reporter: Greg Haber
> Assignee: Barry LaFond
> Attachments: StockQuoteService-ghh.wsdl, StockQuoteService.wsdl
>
>
> If you try to use the Web Service As Relational Importer on the attached StockQuoteService.wsdl file (a sample from the Axis2 1.3 distribution), you'll find that while it passes validation, if on the WSDL Operations Selection screen you leave the selections at their defaults (both of the SOAP 1.1 web services selected, and the SOAP 1.2 web services unchecked), when you press Finish you'll get an NPE. But if you uncheck the "update" service (leaving only getPrice selected), then you can click Finish and create the source model.
> The issue with the "update" operation is that it is an operation with an input but no output. If you modify the WSDL so that this service does indeed have an output (per the StockQuoteService-greg.wsdl attached), both services will import successfully.
> We should be able to handle such operations (ones with no output).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Moved: (TEIIDDES-324) Build relationship between objects (ie. basetable, views, Webservice operator) to artifacts ie( xsd, wsdl, etc..)
by Van Halbert (JIRA)
[ https://jira.jboss.org/jira/browse/TEIIDDES-324?page=com.atlassian.jira.p... ]
Van Halbert moved JBEDSP-434 to TEIIDDES-324:
---------------------------------------------
Project: Teiid Designer (was: JBoss Enterprise Data Services Platform)
Key: TEIIDDES-324 (was: JBEDSP-434)
Component/s: Modeling
(was: Designer)
Affects Version/s: Future
(was: 5.5.3)
> Build relationship between objects (ie. basetable, views, Webservice operator) to artifacts ie( xsd, wsdl,etc..)
> -----------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-324
> URL: https://jira.jboss.org/jira/browse/TEIIDDES-324
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: Future
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
>
> Currently we build relationship between table to table, column to column.
> We want to be able to build relationship between table/Webservice to an file
> artifact. For example, we have a webservice and we store the
> artifacts(WSDL,document etc... ) in the repository relate to that WS. We
> want to be able to relate that WS to that actual WSDL so when the query
> return to the user of the list of WS, we want to display the WSDL so they
> can down load the WSDL as well. Currently the artifact doesn't have
> uuidstring assign to so I don't know if we can build that relationship
> between the objects and the artifacts.
> Issue Tracker ticket 187725
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months