Skip to content

Add type mapping fragment to applicable connectors#8727

Closed
jhlodin wants to merge 1 commit intotrinodb:masterfrom
jhlodin:jl/type-mapping
Closed

Add type mapping fragment to applicable connectors#8727
jhlodin wants to merge 1 commit intotrinodb:masterfrom
jhlodin:jl/type-mapping

Conversation

@jhlodin
Copy link
Copy Markdown
Contributor

@jhlodin jhlodin commented Jul 30, 2021

Add standard type mapping fragment to connector documentation for applicable JDBC connectors

Cherry-picked from fca12fc

@jhlodin
Copy link
Copy Markdown
Contributor Author

jhlodin commented Jul 30, 2021

Should be added to 360 docs

Phoenix table in Trino that uses the ``BINARY`` data type, as Trino
does not have an equivalent type.

.. include:: jdbc-type-mapping.fragment
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the "jdbc-type-mapping" documents things other than JDBC type mapping (eg case-insensitive-name-matching for name mapping, or metadata.cache-ttl for metadata caching).

as such, it is not suitable for inclusion within "Type mapping" section

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm. Would a header like "Data mapping" or even "Data source mapping" be more appropriate then?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Never mind, @hashhar appears to be resolving this in #8643 where he split out the non-type mapping parameters into a different fragment.

@jhlodin jhlodin closed this Aug 2, 2021
@jhlodin jhlodin deleted the jl/type-mapping branch August 4, 2021 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants