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

engine: do not use keywords as keys #32

Merged
merged 1 commit into from Jun 21, 2017

Conversation

kaplun
Copy link
Member

@kaplun kaplun commented Jun 21, 2017

Do not use keywords as dictionary keys, rather as elements in a list.
(Closes inspirehep/inspire-next#2456)

Signed-off-by: Samuele Kaplun samuele.kaplun@cern.ch

Do not use keywords as dictionary keys, rather as elements in a list.
(Closes inspirehep/inspire-next#2456)

Signed-off-by: Samuele Kaplun <samuele.kaplun@cern.ch>
@kaplun kaplun merged commit c2eba23 into inveniosoftware-contrib:master Jun 21, 2017
@michamos
Copy link

won't this fail for the same reason it failed with the experiment guesser (inspirehep/inspire-next#2054)?

@kaplun
Copy link
Member Author

kaplun commented Jun 21, 2017

Well, I now have to adapt inspire-next to it.

@michamos
Copy link

I mean using lists as tuples with different types inside that make ES choke.

@kaplun
Copy link
Member Author

kaplun commented Jun 22, 2017

Ha! Now I understand. I am actually further fixing indeed classifier to properly output list objects rather than list of tuples.

@kaplun kaplun mentioned this pull request Jun 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants