I'll just flatten maps like we do in the JSONMapParser and leave it at
that.  I will not do anything with lists. We can clean this up as part of
METRON-735.

On Fri, Feb 24, 2017 at 11:00 AM, Otto Fowler <[email protected]>
wrote:

> Tells you how much solr stuff we have going on.
> This is all yucky.  Then again I voted for 1.
>
>
>
> On February 24, 2017 at 10:26:52, Nick Allen ([email protected]) wrote:
>
> ​So I don't need to unfold lists, but I do maps?  I thought the commentary
> on METRON-686 was that Solr cannot handle "complex types".  I took that to
> mean both maps and lists.
>
> Yes, Otto. The only reasonable way to unfold a list would be using the
> index of the element.
>
> "list": ["e1", "e2", "e3"]
> ->
> list.0.e1
> list.1.e2
> list.2.e3
>
>
> I don't want to unfold lists or maps. :)​
>
>
>
>
> On Fri, Feb 24, 2017 at 10:17 AM, Otto Fowler <[email protected]>
> wrote:
>
>> No, I don’t think it does.  I am not sure how you would do that, other
>> than putting a number at the end of the unwrapped array item?
>>
>>
>>
>> On February 24, 2017 at 10:12:26, Nick Allen ([email protected]) wrote:
>>
>> Per Otto's advice, I am looking to reuse the normalizer/flattener
>> mechanism
>> that currently exists in JSONMapParser. It looks like the mechanism is
>> built into the class, so I will have to extract it. It looks like landing
>> it in JSONUtils is a logical place.
>>
>> It appears that the mechanism only handles maps, not lists. Is that true?
>> I will need to add similar functionality for lists to reuse this for
>> METRON-686.
>>
>>
>

Reply via email to