teiid-documents | Community documents for Teiid Engine and Teiid Server

by teiid HTML Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | teiid-documents Summary

teiid-documents is a HTML library. teiid-documents has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

Community documents for Teiid Engine and Teiid Server

Support

Quality

Security

License

Reuse

Support

teiid-documents has a low active ecosystem.

It has 12 star(s) with 25 fork(s). There are 8 watchers for this library.

It had no major release in the last 6 months.

There are 0 open issues and 4 have been closed. On average issues are closed in 1 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of teiid-documents is current.

Quality

teiid-documents has no bugs reported.

Security

teiid-documents has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

teiid-documents does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

teiid-documents releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of teiid-documents

Get all kandi verified functions for this library.

teiid-documents Key Features

No Key Features are available at this moment for teiid-documents.

teiid-documents Examples and Code Snippets

No Code Snippets are available at this moment for teiid-documents.

Community Discussions

Trending Discussions on teiid-documents

Teiid Springboot Starter Collation or Locale

How to set max-source-rows-allowed Teiid Springboot

OData $search support in Teiid vs Jboss Data Virtualization

QUESTION

Teiid Springboot Starter Collation or Locale

Asked 2021-Feb-11 at 17:21

Where can I set the locale for translators and what is the accepted format. E.g. I have seen instances where the locale is set as nl_NL, nl-NL. I want to force the locale of Teiid Springboot to be UTF-8 in order to make sure that ORDER BY clauses are correctly pushed down to the source. I figured that I have to set org.teiid.collationLocale, but the documentation for the correct locale points to an outdated Java 6 page. https://teiid.github.io/teiid-documents/master/sb/admin/System_Properties.html

We use the default Teiid Oracle translator and use Hikari for our datasources. The documentation of the translators points to setting the collation for translators in the execution factory; As far as I know we don't use those right now. https://teiid.github.io/teiid-documents/master/sb/dev/Translator_Capabilities.html

What are the steps I should take to force the locale for the engine to UTF-8 and do the same for the translators?

Note: we use a DDL with data wrappers to specify our connection to our Oracle sources.

...

ANSWER

Answered 2021-Feb-11 at 17:21

There is no collation support directly on order by clauses. The best you can do is inform the engine (org.teiid.collationLocale property) what collation it should be using and set a collation execution property on each translator to inform the engine as to what the translator will use, then Teiid can choose not to push orderings if there is a mismatch.

Source https://stackoverflow.com/questions/66028674

QUESTION

How to set max-source-rows-allowed Teiid Springboot

Asked 2021-Jan-06 at 13:44

While scouting the documentation we found the following properties that we want to set.

max-source-rows-allowed
exception-on-max-source-rows

Found on the following page: https://teiid.github.io/teiid-documents/16.0.x/content/admin/Other_Considerations.html

However, we have tried several ways to set these without avail. The properties are not listed on the following page. https://github.com/teiid/teiid-spring-boot/blob/master/docs/Reference.adoc

How can we set these properties?

...

ANSWER

Answered 2021-Jan-06 at 13:44

Teiid spring boot does not currently allow setting properties like these, which are normally set in the Teiid WildFly subsystem, in an elegant way. The only workaround is to wire in your own EmbeddedConfiguration with all the appropriate settings - as the TeiidAutoConfiguration logic won't make any additional changes to a supplied configuration.

You can also log an issue / supply a patch to have this properties set from the configuration file.

Source https://stackoverflow.com/questions/65579872

QUESTION

OData $search support in Teiid vs Jboss Data Virtualization

Asked 2020-Mar-12 at 13:35

I'm looking to use Salesforce to, using Odata, connect to Teiid+Wildfly, which in turn connects to SQL Server.

When I read the documentation for Teiid 13, under limitations, it says OData $search is not supported.

http://teiid.github.io/teiid-documents/13.0.x/content/client-dev/OData4_Support.html

The following feature limitations currently apply.

search is not supported

delta processing is not supported

data-aggregation extension to specification is not supported

$it usage is limited to only primitive collection properties

However when I read the documentation for Jboss Data Virtualization, under limitations, it doesn't list that $search is not supported.

https://access.redhat.com/documentation/en-us/red_hat_jboss_data_virtualization/6.4/html/development_guide_volume_1_client_development/ch08s02

The following feature limitations apply:

Delta processing is not supported.

The data-aggregation extension to the specification is not supported."

Anyone know why there's a difference? Does the paid JBoss flavour have extra code allowing OData $search parameters?

Thanks in advance.

...

ANSWER

Answered 2020-Mar-12 at 13:35

$search is not available in the JBoss Data Virtualization either, I would think it is a documentation issue.

The reason $search is not implemented as $search expected to works on all the content like cache search, which would be a very expensive operation in Teiid as it does not hold any content. I would think one needs an Elastic Search like backend integration to support for this where all the content is also cached.

Source https://stackoverflow.com/questions/60629647

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install teiid-documents

The .travis.yaml file allows for continuous integration of doc changes on multiple branches to be published to a single gh-pages branch. When you setup the travis build job you must create the gh-pages branch if it does not already exist:. You will need to add an appropriate user and git api key with repo access as the environment properties GITHUB_USER and GITHUB_API_KEY respectively in the travis build settings.

Support

The documentation project is hosted on GitHub at (teiid/teiid-documents). It is published on GitHub Pages at (teiid.github.io/teiid-documents/master/content) ('master' can be substituted with any maintained branch e.g. '10.3.x'). For simple changes you can just use the online editing capabilities of GitHub by navigating to the appropriate source file and selecting fork/edit.

Find more information at: