I can't trace back to see what would possible cause getUserData() to return
an empty Object, but that appears to be what is happening?
For these severs, indexes that are pre-optimized are shipped over to the
server and the server is re-started... nothing is actually ever committed
on these live servers. This should behave exactly the same for artists and
tracks, even though tracks is the one always missing lastUpdated.
Re: One of three cores is missing userData and lastModified fields from /admin/cores
Were you able to get a solution to this issue ?
Aaron Daubman wrote
> On a Solr server running 4.10.2 with three cores, two return the expected
> info from /solr/admin/cores?wt=json but the third is missing userData and
> The first (artists) and third (tracks) cores from the linked screenshot
> the ones I care about.
> Unfortunately, the third (tracks) is the one missing
> As far as I can see, that comes from:
> https://github.com/apache/lucene-solr/blob/lucene_solr_4_10_2/solr/core/src/java/org/apache/solr/handler/admin/LukeRequestHandler.java#L568 >
> I can't trace back to see what would possible cause getUserData() to
> an empty Object, but that appears to be what is happening?