Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
7.1.0, 7.0.2
-
Triaged
-
1
-
Unknown
Description
ALTER INDEX `travel-sample`.country_idx
WITH
Will fail when encryption is enabled.
The issues was introduced where we started supporting the use of encrypted ports from the query. We were only using un encrypted port numbers always.
The design is to support
- only un encrypted port numbers when encryption was disabled
- both un-encrypted and encrypted port numbers when encryption was set to all
- only encrypted port numbers when encryption was strict
But after the change only encrypted ports are working in encryption mode all which breaks backwards compatibility.
Attachments
Issue Links
- backports to
-
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
ALTER INDEX `travel-sample`.country_idx
WITH {"action": "replica_count", "num_replica": 2, "nodes": ["127.0.0.1:9001", "127.0.0.1:9002", "127.0.0.1:9003"]} Will fail when encryption is enabled. |
ALTER INDEX `travel-sample`.country_idx
WITH {"action": "replica_count", "num_replica": 2, "nodes": ["127.0.0.1:9001", "127.0.0.1:9002", "127.0.0.1:9003"]} Will fail when encryption is enabled. The issues was introduced where we started supporting the use of encrypted ports from the query. We were only using un encrypted port numbers always. The design is to support * only un encrypted port numbers when encryption was disabled * both un-encrypted and encrypted port numbers when encryption was set to all * only encrypted port numbers when encryption was strict But after the change only encrypted ports are working in encryption mode all which breaks backwards compatibility. |
| Description |
ALTER INDEX `travel-sample`.country_idx
WITH {"action": "replica_count", "num_replica": 2, "nodes": ["127.0.0.1:9001", "127.0.0.1:9002", "127.0.0.1:9003"]} Will fail when encryption is enabled. The issues was introduced where we started supporting the use of encrypted ports from the query. We were only using un encrypted port numbers always. The design is to support * only un encrypted port numbers when encryption was disabled * both un-encrypted and encrypted port numbers when encryption was set to all * only encrypted port numbers when encryption was strict But after the change only encrypted ports are working in encryption mode all which breaks backwards compatibility. |
ALTER INDEX `travel-sample`.country_idx
WITH {"action": "replica_count", "num_replica": 2, "nodes": ["127.0.0.1:9001", "127.0.0.1:9002", "127.0.0.1:9003"]} Will fail when encryption is enabled. The issues was introduced where we started supporting the use of encrypted ports from the query. We were only using un encrypted port numbers always. The design is to support * only un encrypted port numbers when encryption was disabled * both un-encrypted and encrypted port numbers when encryption was set to all * only encrypted port numbers when encryption was strict But after the change only encrypted ports are working in encryption mode all which breaks backwards compatibility. |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Assignee | Sai Krishna Teja [ JIRAUSER25045 ] | Girish Benakappa [ girish.benakappa ] |
| Assignee | Girish Benakappa [ girish.benakappa ] | Hemant Rajput [ hemant.rajput ] |
| Labels | needs_automation |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Closed [ 6 ] | Reopened [ 4 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Reopened [ 4 ] | Resolved [ 5 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |