lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-7076) MIGRATE/CHANGES.txt need improved Points verbage
Date Wed, 09 Mar 2016 17:07:40 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-7076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187416#comment-15187416
] 

Robert Muir commented on LUCENE-7076:
-------------------------------------

Also any {{@deprecated}} warnings need to be clear and point to the best place.

For example LegacyNumericRangeQuery leads you instead to PointRangeQuery, but that is not
the place to send the user.

> MIGRATE/CHANGES.txt need improved Points verbage
> ------------------------------------------------
>
>                 Key: LUCENE-7076
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7076
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Robert Muir
>         Attachments: LUCENE-7076.patch
>
>
> for MIGRATE.txt, we should have some more verbage, maybe examples of how to index/search
a 1D integer. maybe even better, it could be done in javadocs and referenced here as well.
> CHANGES.txt I think we should organize so it looks more like changes entry for flexible
indexing or other similar big changes, and there is a coherent summary of what happened.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message