Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DATAREDIS-1062] : Disable select dbIndex in case dbIndex is 0 #496

Conversation

tamilselvan-chinnaswamy
Copy link
Contributor

@tamilselvan-chinnaswamy tamilselvan-chinnaswamy commented Nov 12, 2019

https://jira.spring.io/browse/DATAREDIS-1062

When shareNativeConnection was set to false and enabled connection pooling before executing each redis command, select dbIndex command was executed. this is un-necessary call. since my application was configured to use single database and i don't want to select a database every time.

  • You have read the Spring Data contribution guidelines.
  • There is a ticket in the bug tracker for the project in our JIRA.
  • You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
  • You submit test cases (unit or integration tests) that back your changes.
  • You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).

When shareNativeConnection was set to false and enabled connection pooling before executing each redis command, select dbIndex command was executed. this is un-necessary call. since my application was configured to use single database and i don't want to select a database every time.
@pivotal-issuemaster
Copy link

@tamilselvan-chinnaswamy Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@tamilselvan-chinnaswamy tamilselvan-chinnaswamy changed the title Disable select dbIndex in case dbIndex is 0 [DATAREDIS-1062] : Disable select dbIndex in case dbIndex is 0 Nov 12, 2019
@pivotal-issuemaster
Copy link

@tamilselvan-chinnaswamy Thank you for signing the Contributor License Agreement!

mp911de pushed a commit that referenced this pull request Nov 22, 2019
When shareNativeConnection was set to false and enabled connection pooling before executing each Redis command, select dbIndex command was executed. Selecting the database can be superfluous when the connection already uses the right database index.

Original pull request: #496.
mp911de added a commit that referenced this pull request Nov 22, 2019
We now select the database on dedicated connection acquisition only if the current database is different from the default database. Database connections are expected to use the default database index when they are acquired so the database index may be changed for the duration when a connection is in use.
We also reset dedicated connections to use the default database index on connection cleanup to bring the connection back into its initial state.

Add author tag and tests.

Original pull request: #496.
mp911de pushed a commit that referenced this pull request Nov 22, 2019
When shareNativeConnection was set to false and enabled connection pooling before executing each Redis command, select dbIndex command was executed. Selecting the database can be superfluous when the connection already uses the right database index.

Original pull request: #496.
mp911de added a commit that referenced this pull request Nov 22, 2019
We now select the database on dedicated connection acquisition only if the current database is different from the default database. Database connections are expected to use the default database index when they are acquired so the database index may be changed for the duration when a connection is in use.
We also reset dedicated connections to use the default database index on connection cleanup to bring the connection back into its initial state.

Add author tag and tests.

Original pull request: #496.
@mp911de
Copy link
Member

mp911de commented Nov 22, 2019

Thank you for your contribution. That's merged, polished, and backported now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants