[
https://issues.redhat.com/browse/TEIIDSB-192?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIIDSB-192:
----------------------------------------
https://github.com/teiid/teiid-spring-boot/pull/223 adds the salesforce 41 and 34
translator names as migration targets as well by adding additional aliases for the
salesforce connection factory. At this point I believe we have our bases covered in terms
of allowing existing names to simply work without a manual effort or specific migration
logic. The things that could be documented:
* just like the warning in teiid, say that if the saleforce url is not specified it is not
guaranteed across releases which api version you are hitting. also we can note the
difference of having just a single translator supported - I'll handle that in the base
Teiid docs with templating.
* update whatever documentation may exist as to the full set of names as the base docs
don't mention anything about the driver specific x-db names nor for now athena.
Document migration for alias names
----------------------------------
Key: TEIIDSB-192
URL:
https://issues.redhat.com/browse/TEIIDSB-192
Project: Teiid Spring Boot
Issue Type: Task
Components: documentation
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Priority: Major
Fix For: 1.5.0
Original Estimate: 4 hours
Time Spent: 2 hours
Remaining Estimate: 2 hours
Translators like salesforce and actian-vector has new name in the spring boot, we need to
either document or switch back to original names.
Also if we are updating migration utilities we can build in smarts into it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)