[ https://issues.apache.org/jira/browse/LUCENE-7738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906274#comment-15906274 ]
Nicholas Knize commented on LUCENE-7738: ---------------------------------------- Thanks [~dsmiley]! I have no problem putting both {{InetAddressRangeField}} and {{InetAddressPoint}} in the misc module. Seems like a sound justification to me. I also think I'm going to refactor all range field classes to remove {{Field}} from the class name. It seems more natural (to me) to have {{Point}} and {{Range}} counterparts (e.g., {{DoublePoint}}, {{DoubleRange}}, {{InetAddressPoint}}, {{InetAddressRange}})? (and less typing is always a bonus) What do you think? (or does anyone care? - I know naming is often an exercise in bikeshedding) If no one objects I can open a separate issue to "Graduate Range Fields from sandbox" that will refactor the range field class names and move them to the appropriate module? What does everyone think? > Add new InetAddressRangeField > ----------------------------- > > Key: LUCENE-7738 > URL: https://issues.apache.org/jira/browse/LUCENE-7738 > Project: Lucene - Core > Issue Type: New Feature > Reporter: Nicholas Knize > Attachments: LUCENE-7738.patch, LUCENE-7738.patch > > > This issue adda a new {{InetAddressRangeField}} for indexing and querying > InetAddress ranges. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org