Indra Client: Unrecognized field "mt" about indra

[julsal]

Hi @blang, thanks for the notification. In fact, we are working on a new high-changed version, which is expected to be ready in few days.

I guess the commit f81cfb4 from my fork (branch pp_filter) is free of bugs. It might be useful for you now.

[blang]

Hi @julsal, thanks for the quick response. I'll have a look at the commit you mentioned.
It's pretty late in my project so i just need a stable pair relatedness.
I managed to get the request working by crafting the request by myself which was the quickest option for now.
The only question remains if the backend (lambdacube/indra:2.0.2) is stable in this situation (only pair requests)
Any experience with this version?

To use your commit f81cfb4, is a backend (docker) update necessary or does it work with lambdacube/indra:2.0.2?

Thanks,
Best,
Ben

[julsal]

Hi @blang, yes it is a large backend update. In the case that you managed to work with the current version, I don't recommend updating now. I hope up to the next week we have a new well-tested version.
Best,

[blang]

@julsal Ok thank you, i will stay with the current version. I was using a much older version of indra for development and was forced to update since the w2v-wiki2014 dataset for the old mongo version was no longer available on the dataset server.
If the current version does not work properly, i will have to downgrade again.
Are the old python updater based datasets for the old mongo version still available online?

[julsal]

@blang For sure it is available in the one of the versions of https://github.com/Lambda-3/IndraComposed, but unfortunately I can't precise the version.

[julsal]

The new version solves this problem.