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

MB-62400: Allow vector and numeric aliases for the same field #2055

Merged
merged 1 commit into from
Jul 25, 2024

Conversation

Likith101
Copy link
Member

  • Removed logic that prevents numeric field mappings to be executed after a vector field has been detected
  • Added checks to walk document on non vector field types preserving previous logic

 - Removed logic that prevents numeric field mappings to be executed after a
vector field has been detected
 - Added checks to walk document on non vector field types preserving previous logic
isPropertyVectorInitialized = true
} else {
isPropertyVector = isPropertyVector && processed
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Likith101 I believe @CascadingRadium added this and my memory on this is somewhat hazy - it seems we did this to avoid having to process a vector field multiple times, I like your code proposal here which is simple and easy to follow - just want to make sure we're not inadvertently dropping any optimization here.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I collaborated with @CascadingRadium on this and we made sure to preserve any existing behaviour that was present before vectors and only remove the double processing for vector fields.

@abhinavdangeti abhinavdangeti added this to the v2.4.2 milestone Jul 24, 2024
@abhinavdangeti abhinavdangeti merged commit ecfd7fb into master Jul 25, 2024
9 checks passed
@abhinavdangeti abhinavdangeti deleted the mapTwice branch July 25, 2024 16:30
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