[#LUCENE-1349] Mark Fieldable as allowing some changes in 2.x future releases

Lucene - Java

Mark Fieldable as allowing some changes in 2.x future releases

Created: 04/Aug/08 01:06 PM Updated: 05/Aug/08 12:30 PM

Return to search

Component/s:

None

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

File Attachments:

	File Name	Date Attached	Attached By	Size
	LUCENE-1349.patch	2008-08-04 01:30 PM	Grant Ingersoll	2 kB

Issue Links:

Blocker

This issue blocks:

~~LUCENE-1340~~ Make it posible not to include TF information in index

~~LUCENE-1219~~ support array/offset/ length setters for Field with binary data

Lucene Fields:	New
Resolution Date:	05/Aug/08 12:30 PM

Description

« Hide

See http://lucene.markmail.org/message/4k2gqs3n7coh4lmd?q=Fieldable

1. We mark Fieldable as being subject to change. We heavily advertise (on java-dev and java-user and maybe general) that in the next minor release of Lucene (2.4), Fieldable will be changing. It is also marked at the top of CHANGES.txt very clearly for all the world to see. Since 2.4 is probably at least a month away, I think this gives anyone with a pulse enough time to react.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

[ Permlink | « Hide ]

Grant Ingersoll added a comment - 04/Aug/08 01:30 PM

Draft.

[ Permlink | « Hide ]

Michael McCandless added a comment - 05/Aug/08 10:15 AM

Looks good Grant.

Maybe cancel out the double-negative in:

It will, however, not mean that a new version of the Lucene can't read an old version within the same major version.

to something like this (rough draft)?

This change only affects the Fieldable API; other backwards
compatibility promises remain intact. For example, Lucene can still
read and write indices created within the same major version.

[ Permlink | « Hide ]

Grant Ingersoll added a comment - 05/Aug/08 12:30 PM

Committed revision 682689.