TermVectors not displayed if field isn't stored

[GoogleCodeExporter]

*What steps will reproduce the problem?*
Index a document and for a Field set this options
 new Field("myFieldName", "fieldcontent" Store.NO, Index.ANALYZED, Field.TermVector.YES

*What is the expected output? What do you see instead?*
TermVectors are stored into the indes, but Luke can't show them in the "Browse 
By Document" tab, only stored fields seems to be displayed.

*What version of the product are you using? On what operating system?*
LukeAll-1.0.1.jar, Windows7, using latest Java JRE

Original issue reported on code.google.com by thePanz@gmail.com on 30 Jun 2010 at 1:55

[GoogleCodeExporter]

I'm also seeing this... I have the .prx index, but can't view it in Luke

Original comment by seanphur...@gmail.com on 16 Jul 2010 at 3:31

[GoogleCodeExporter]

I'm hitting this as well. As a workaround, you can use "Reconstruct & Edit" to 
see all of the fields, but this less than optimal.

Original comment by d...@missingmass.com on 5 Apr 2011 at 5:46

[GoogleCodeExporter]

Great tool, but this bug was keeping me from the main use that I wanted it for 
so I tracked it down.  The bug is on line 2514 of Luke.java for the 3.5.0 
source.

    for (int i = 0; i < idxFields.length; i++) {
      Fieldable[] fields = doc.getFieldables(idxFields[i]);
-->     if (fields == null) {
        addFieldRow(table, idxFields[i], null, docid);

doc.getFieldables returns an empty array when the field isn't stored, never 
null(doc.getFieldable returns null)  So the line should be

    if (fields.length == 0) {

I tested this change and it seemed to work ok.

Original comment by doug.ba...@gmail.com on 21 Feb 2012 at 1:47

[GoogleCodeExporter]

any updates? (bug is still in 4-alpha)

Original comment by khame...@gmail.com on 25 Jul 2012 at 3:44

[GoogleCodeExporter]

I fixed this now in trunk rev. 85 - thank you for your patience. For now, 
please build a binary yourself, this fix will be included in the next 
maintenance version.

Original comment by sig...@gmail.com on 25 Jul 2012 at 10:22

• Changed state: Fixed

[GoogleCodeExporter]

many thanks, indeed the problematic field is now appeared, ...but still no way 
to look into its content: <not present or not stored>. Hm, perhaps one should 
use "reconstruct" for such fields... 

Original comment by khame...@gmail.com on 25 Jul 2012 at 10:35

[GoogleCodeExporter]

If this field in this particular doc indeed has a term vector stored then you 
should be able to see it .. can you please build a tiny index that would 
exhibit this problem and attach it here?

Original comment by sig...@gmail.com on 25 Jul 2012 at 10:45