-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Support zone ID in IPv6 addresses. Issue #37107 #37547
Conversation
…t can be converted back to its input
further commits will treat it accordingly
* master: Deprecate _type from LeafDocLookup (elastic#37491) Allow system privilege to execute proxied actions (elastic#37508) Update Put Watch to allow unknown fields (elastic#37494) AwaitsFix testAddNewReplicas SQL: Add protocol tests and remove jdbc_type from drivers response (elastic#37516) SQL: [Docs] Add an ES-SQL column for data types (elastic#37529) IndexMetaData#mappingOrDefault doesn't need to take a type argument. (elastic#37480) Simplify + Cleanup Dead Code in Settings (elastic#37341) Reject all requests that have an unconsumed body (elastic#37504) [Ml] Prevent config snapshot failure blocking migration (elastic#37493) Fix line length for aliases and remove suppression (elastic#37455) Add SSL Configuration Library (elastic#37287) SQL: Remove slightly used meta commands (elastic#37506) Simplify Snapshot Create Request Handling (elastic#37464) Remove the use of AbstracLifecycleComponent constructor elastic#37488 (elastic#37488) [ML] log minimum diskspace setting if forecast fails due to insufficient d… (elastic#37486)
* master: SQL: Lowercase the datatypes in validation error msgs (elastic#37524) DedicatedClusterSnapshotRestoreIT to Zen2 (elastic#37489) SQL: Lowercase es data type (mapping) returned from SQL Commands (elastic#37531) Remove SYS CATALOGS leftover SQL: Describe aliases as views (elastic#37496)
Pinging @elastic/es-core-features |
@camilin87 - thanks for the PR. However, until we address the comment here: #37107 (comment) we should hold off on this PR. I am hesitant to proceed with this change in the common library since it touches so much of the code base. In particular, I am concerned about data manipulation (loosing information) when indexed. I will re-open a discussion about our support (or lack there-of) of zoneId. |
…ne ID to be returned
* master: Change file descriptor limit to 65535 (elastic#37537) Increase timeout for testAddNewReplicas
* issue_37107: Change file descriptor limit to 65535 (elastic#37537) Increase timeout for testAddNewReplicas
I know this issue may need some discussion. That being said. I understand if after your discussions this issue is no longer relevant The updated PR makes sure to read the zone ID Here's a summary of the changes
|
@camilin87 - We appreciate your contribution here, and have discussed this internally. We landed on implementing an ingest node processor to help handle IPv6 zone_ids. I have logged #38064. I am going to close this PR as we heading a different direction. Feel free to pick up that issue if you like and ping me directly with question or reviews. |
Getting this issue on latest version (installation this weekend) |
Issue #37107 describes problems with IPv6 addresses that contain a zone ID.
The scope of this PR is to ignore the zone ID if any.
This on itself will address the reported bug.
Keep in mind this is the first PR of a series. Subsequent PR will properly read the zone ID and construct IPv6 addresses correctly.
Here's a summary of the code changes