[
https://issues.redhat.com/browse/TEIIDSB-192?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIIDSB-192:
----------------------------------------
The convention we have now is [something-]source where something is either a company or
driver name.
Other than ensuring Teiid Spring Boot documentation is aligned with the last set of
changes, that just leaves us with Salesforce as an issue. It would be great if the user
were abstracted from the implementation details of the translator/source - that is they
would specify that salesforce connectivity to api version x is needed and then we'd
select the appropriate translator / source version to support that (typically a given sf
api library will support a range of api versions). However we haven't required the
version to be specified (via the url) and there are obviously a lot of versions that we
wouldn't support - currently Teiid Spring Boot only knows of a single translator
version.
On the other hand one possible solution is to document that by not specifying a url you
are at the mercy of Teiid Spring Boot as to which api version it will use.
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)