Tim-Brooks opened a new pull request, #16115:
URL: https://github.com/apache/lucene/pull/16115

   A ColumnBatch where two columns share the same field name has no
   coherent semantics: each Column carries one IndexableFieldType, so two
   same-named columns would race to feed the same writers under one
   accumulated schema. The intended way to express multi-value is a single
   column whose tuple cursor emits multiple values per batch doc-id.
   
   IndexingChain.processBatch now reserves a fresh batchGen from
   nextFieldGen and rejects any column whose PerField was already tagged
   with that gen in the same batch's first pass. The check sits after the
   existing parentPf reserved-name check so reserved-name errors keep
   their dedicated message. Cross-batch reuse of a field name is
   unaffected since each batch consumes a strictly larger gen.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to