Hi Jianxiong, this is definitely interesting.
Briefly reviewing the paper you linked the use case seems clear :
You want similar "family" of features, to be calculated on each field.
Let's take as example the TF feature, you may want to define in the
features.json only one feature including all
Hi, Michael,
Thank for very valuable feedbacks.
> You can pass in different params in the
> features.json config for each feature, even though they use the same
> feature class.
I used this idea to extract some features in this paper
Hi Jianxiong,
What you say is true. If you want 100 different feature values extracted,
you need to specify 100 different features in the
features.json config so that there is a direct mapping of features in and
features out. However, you more than likely need
to only implement 1 feature class
Hi,
I found that solr learning-to-rank (LTR) supports only ONE feature
for a given feature extractor.
See interface:
https://github.com/apache/lucene-solr/blob/master/solr/contrib/ltr/src/java/org/apache/solr/ltr/feature/Feature.java
Line (281, 282) (in FeatureScorer)
@Override
public
