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

[Search] Cannot use properly custom types #24

Open
c3dr0x opened this issue Aug 6, 2018 · 0 comments
Open

[Search] Cannot use properly custom types #24

c3dr0x opened this issue Aug 6, 2018 · 0 comments

Comments

@c3dr0x
Copy link
Member

c3dr0x commented Aug 6, 2018

Issue

I want to use the GeoPoint capabilites of ES.
If I give a column on my document the type GeoLocation from Nest. It is not mapped to the geopoint automatically because of the way the ElasticMappingFactory works. It mapped to a myPoint.latitute & myPoint.longitude columns.

Temp Solution

I had to import the ElasticMappingFactory in my project & tweak it by adding the following code the existing cases:

                case SearchFieldCategory.GeoPoint:
                    return selector.GeoPoint(x => x
                        .Name(fieldName)
                        .Store(false));

Final solution

Even if adding that case in kinetix.search would be great. I'd want a way to be able to custom the way fields are mapped within my project. ex: I'd want to use complex columns for some advanced cases.

Like what we did for the Domain add a ElasticCustomMappingFactory that would act as an extension for some custom cases.

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

No branches or pull requests

1 participant