[ https://issues.apache.org/jira/browse/LUCENE-7738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906343#comment-15906343 ]
David Smiley commented on LUCENE-7738: -------------------------------------- RE naming; some consistency is good. So if the non-range variant doesn't have 'Field' then don't put it on the range variant. But vice-versa is also true -- consistency being most important. I care little wether both should have (or not have) a "Field" suffix. There seems to be a lot of variation across Lucene, unfortunately. bq. 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? +1 > 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