[
https://issues.apache.org/jira/browse/METRON-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16444320#comment-16444320
]
ASF GitHub Bot commented on METRON-1526:
----------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/995
Before going down the path of partial document update:
* Can you confirm that this isn't an issue when you set docValues to false,
like in my previous comment?
* Are date fields polyfields?
* Is this a problem in 5.x or just 6.x?
* Is there a workaround for dates like there is for latlon in 6.x (e.g.
another type)? If so, wouldn't differentiating schema per version solve the
issue?
If you did want to go with partial updates:
* how do you propose to pull the JSON Patch apart into just the selected
fields?
* Since we will possibly expose these generated fields (perhaps not for
latlon, but possibly for other polytypes), aren't we in the same spot of having
a way to update both a generated field and a derived field if the users can
update derived fields?
* If the answer to that is to whitelist updates on derived fields, aren't
we back in the same spot as we are currently in?
> Location field types cause DocValuesField appear more than once error
> ---------------------------------------------------------------------
>
> Key: METRON-1526
> URL: https://issues.apache.org/jira/browse/METRON-1526
> Project: Metron
> Issue Type: Bug
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
> Priority: Major
>
> While testing [https://github.com/apache/metron/pull/970] I get this error
> when creating a meta alert:
> {code:java}
> Error from server at http://10.0.2.15:8983/solr/bro: Exception writing
> document id bbc150f5-92f8-485d-93cc-11730c1edf31 to the index; possible
> analysis error: DocValuesField
> \"enrichments.geo.ip_dst_addr.location_point_0_coordinate\" appears more than
> once in this document (only one value is allowed per field){code}
> I tracked it down to the fact that multiple fields are returned for a
> location field. For example when a field named
> "enrichments.geo.ip_dst_addr.location_point" is configured in a schema, these
> fields are returned in a query:
> {code:java}
> {
> "enrichments.geo.ip_dst_addr.location_point_0_coordinate": "33.4499",
> "enrichments.geo.ip_dst_addr.location_point_1_coordinate": "-112.0712",
> "enrichments.geo.ip_dst_addr.location_point": "33.4499,-112.0712"
> }
> {code}
> We need a way to either suppress these extra fields when querying or remove
> them before updating a document.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
