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

feat(elasticsearch): improve mappings - EUBFR-88 #55

Merged
merged 3 commits into from Dec 13, 2017

Conversation

kalinchernev
Copy link
Contributor

@kalinchernev kalinchernev commented Dec 8, 2017

Todos after feedback from Rainer:

Deployed stage chernka30, so far do not yield errors on portal side => works.
I'm awaiting some additional feedback from Rainer if there are some other tweaks necessary before we merge as test stage is frozen for the time being.

@kalinchernev
Copy link
Contributor Author

Removing the wip label as Rainer hasn't reported any issues with current implementation.
Geospatial follow-up on EUBFR-97, EUBFR-98 and also EUBFR-99 is to help Rainer with specific search queries as in current portal.

@@ -7,6 +7,8 @@ import split2 from 'split2';

import deleteProjects from '../lib/deleteProjects';
import SaveStream from '../lib/SaveStream';
// elasticsearch mapping https://goo.gl/MEGiA6
Copy link
Contributor

Choose a reason for hiding this comment

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

Please don't use Google's URL shortener... please...

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I didn't find one for the EC and links are sometimes too long and ugly

project_locations: {
properties: {
location: {
type: 'geo_point',
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'd suggest this change to happen in EUBFR-98 where we ensure the transform is also updated?

properties: {
location: {
type: 'geo_point',
ignore_malformed: true,
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a specific reason for ignore_malformed: true?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This one I added before we make latitude and longitude 0 if not available. If a value is not 0, but null and type is geo_something as in most defaults in our case, indexing fails and stops the process.

@kalinchernev kalinchernev force-pushed the feat/elasticsearch-mapping-EUBFR-88 branch from 5ed8c9c to a7582e4 Compare December 13, 2017 14:49
@kalinchernev kalinchernev merged commit 8a67c11 into master Dec 13, 2017
@kalinchernev kalinchernev deleted the feat/elasticsearch-mapping-EUBFR-88 branch December 13, 2017 15:08
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.

None yet

2 participants