[AMBARI-23869] Inconsistent datatypes error when authenticating users when Oracle is the backend database for Ambari #1330
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… when Oracle is the backend database for Ambari
rlevas
requested review from
zeroflag,
mpapirkovskyy,
a user,
jonathan-hurley and
smolnar82
|
Refer to this link for build results (access rights to CI server needed): |
jonathan-hurley
approved these changes
May 20, 2018
smolnar82
approved these changes
May 21, 2018
ghost
approved these changes
May 21, 2018
|
This is for AMBARI-23829. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Inconsistent datatypes error when authenticating users when Oracle is the backend database for Ambari:
This occurs when selecting from the user_authentication table when the where clause compares a string with value from the authentication_key column. The solution was to convert the CLOB/TEXT column to a VARCHAR(2048) column for all database.
Also fixed an error encountered when installing the Ambari DDL into a MySQL/MariaDB server.
How was this patch tested?
Manually tested the following scenarios:
Please review Ambari Contributing Guide before opening a pull request.