Hi,
I use it in production with numTerms=0 parameter set.
Ahmet
On Thursday, December 4, 2014 10:48 PM, Constantin Wolber
wrote:
Hi,
Basically using an endpoint in the admin section is something that makes me
think if there is an alternative.
And it would have been nice to have a straight
Hi,
Basically using an endpoint in the admin section is something that makes me
think if there is an alternative.
And it would have been nice to have a straight forward resource oriented
approach. Which the Luke certainly is not.
Regards
Constantin
> Am 04.12.2014 um 20:46 schrieb Chris
: I did not oversee a feature of the rest endpoints. So probably we will
: stick with the admin/luke endpoint to achieve our goal.
Ok ... i mean ... yeah -- the /admin/luke endpoint exists to tell you what
fields are *actually* in your index, regardless of who/how they are in
your index.
the
Hi,
And thanks for the answers. So my understanding is at least correct that I did
not oversee a feature of the rest endpoints. So probably we will stick with the
admin/luke endpoint to achieve our goal.
Since you have been telling me a lot about the xy problem, I will of course
give you some
: Subject: REST API Alternative to admin/luke
this smells like an XY problem ... if /admin/luke gives you the data you
want, why not use /admin/luke ? ... what is it about /admin/luke that
prevents you from solving your problem? what is your ultimate goal?
: If I use the admin/luke URL all tho
On 12/4/2014 8:20 AM, Constantin Wolber wrote:
> we use dynamic Fields in our schema.
>
>
>
> If I use the admin/luke URL all those dynamic fields are listed with
> their actual name.
>
>
>
> If I use the rest endpoint /schema/fields only the hard coded fields
> are returned. And dynamicFields
