Re: Solr Paryload example

Hi all, I’ve prepared the pull request and submitted the issue. https://issues.apache.org/jira/browse/SOLR-13863 If anyone is interested in the

Re: Solr Paryload example

Hi all, just to let you know that we started using spayload function in our quality environment for testing. Within a couple of weeks the feature will be deployed in production. Best regards, Vincenzo On Wed, Oct 23, 2019 at 4:31 PM Vincenzo D'Amore wrote: > Hi Erick, yes, absolutely, it's a

Re: Solr Paryload example

Hi Erick, yes, absolutely, it's a great pleasure for me contribute. On Wed, Oct 23, 2019 at 2:25 PM Erick Erickson wrote: > Bookmarked. Do you intend that this should be incorporated into Solr? If > so, please raise a JIRA and link your PR in…. > > Thanks! > Erick > > > On Oct 22, 2019, at 6:56

Re: Solr Paryload example

Bookmarked. Do you intend that this should be incorporated into Solr? If so, please raise a JIRA and link your PR in…. Thanks! Erick > On Oct 22, 2019, at 6:56 PM, Vincenzo D'Amore wrote: > > Hi all, > > this evening I had some spare hour to spend in order to put everything > together in a

Re: Solr Paryload example

Hi all, this evening I had some spare hour to spend in order to put everything together in a repository. https://github.com/freedev/solr-payload-string-function-query On Tue, Oct 22, 2019 at 5:54 PM Vincenzo D'Amore wrote: > Hi all, > > thanks for supporting. And many thanks whom have

Re: Solr Paryload example

Hi all, thanks for supporting. And many thanks whom have implemented the integration of the github Solr repository with the intellij IDE. To configure the environment and run the debugger I spent less than one hour, (and most of the time I had to wait the compilation). Solr and you guys really

Re: Solr Paryload example

Yes. The decoding of a payload based on its schema type is what the payload() function does. Your Payloader won't currently work well/legibly for fields encoded numerically: https://github.com/o19s/payload-component/blob/master/src/main/java/com/o19s/payloads/Payloader.java#L130

Re: Solr Paryload example

Have you checked out https://github.com/o19s/payload-component On Mon, Oct 21, 2019 at 2:47 PM Erik Hatcher wrote: > How about a single field, with terms like: > > store1_USD|125.0 store2_EUR|220.0 store3_GBP|225.0 > > Would that do the trick? > > And yeah, payload decoding is currently

Re: Solr Paryload example

How about a single field, with terms like: store1_USD|125.0 store2_EUR|220.0 store3_GBP|225.0 Would that do the trick? And yeah, payload decoding is currently limited to float and int with the built-in payload() function. We'd need a new way to pull out textual/bytes payloads - like

Re: Solr Paryload example

My tongue-in-cheek comment about how to tell veteran programmers from novices: Novice: “My code compiled fine, it should run perfectly” Veteran: “That can’t be right, my code appeared to succeed the first time I ran it.”... > On Oct 21, 2019, at 12:54 PM, Vincenzo D'Amore wrote: > > Hi all,

Re: Solr Paryload example

On 10/21/2019 7:59 AM, Vincenzo D'Amore wrote: But how many dynamic fields like this can I have? more than thousands? There are no actual limits on the number of fields, dynamic or not. You can have as many fields as you want per document, and as many fields as you want across the whole

Re: Solr Paryload example

Hi all, at last I've tried to write my own payload function, and it has worked (pretty well) immediately! Well, to be honest I'm a little puzzled, so I have applied immediately the first rule: always beware when your code works at first run. Now I'm testing it. On Mon, Oct 21, 2019 at 4:37 PM

Re: Solr Paryload example

Don’t go to thousands of fields, it’s usually a bad idea for that many fields. If all you’re doing is returning the data for display, have you considered indexing, perhaps in a separate field, a string token for each? Something like store1_USD_125.00 ? Then have the UI split that apart in a

Re: Solr Paryload example

I remember several years ago a discussion/blog post about a similar problem. The author went through a lot of thinking and decided that the best way to deal with a similar problem was to have Solr documents represent different level of abstraction, more granular. IIRC, the equivalent for your

Re: Solr Paryload example

Hi Erick, thanks for getting back to me. We started to use payloads because we have the classical per-store pricing problem. Thousands of stores across and different prices. Then we found the payloads very useful started to use it for many reasons, like enabling/disabling the product for such

Re: Solr Paryload example

This is one of those situations where I know a client did it, but didn’t see the code myself. So I can’t help much. Perhaps a good question at this point, though, is “why do you want to add string payloads anyway”? This isn’t the client, but it might give you some pointers:

Re: Solr Paryload example

Hi Erick, It seems I've reached a dead-point, or at least it seems looking at the code, it seems I can't easily add a custom decoder: Looking at PayloadUtils class there is getPayloadDecoder method invoked to return the PayloadDecoder : public static PayloadDecoder

Re: Solr Paryload example

Thanks Eric, please, do you have a clue or a suggestion to give me in order to write such function? Or should I write a payload decoder for the delimited_payloads_string. And again, if I have to write a decoder, would be easier if I found an example to start with. Best regards, Vincenzo On Mon,

Re: Solr Paryload example

You’d need to write one. Payloads are generally intended to hold numerics you can then use in a function query to factor into the score… Best, Erick > On Oct 20, 2019, at 4:57 PM, Vincenzo D'Amore wrote: > > Sorry, I just realized that I was wrong in how I'm using the payload > function. >