Thank you Tim, Best regards Evgeni
On Monday, November 26, 2018 at 6:22:56 PM UTC+2, Tim Donohue wrote: > > Hi Evgeni, > > As noted in your other email thread about this Solr schema issue, we > already have a ticket to fix this. See: > https://jira.duraspace.org/browse/DS-4066 and > https://github.com/DSpace/DSpace/pull/2249 > > These changes have already been applied to both 6.x (to be released in > 6.4) and 7.x. So, as long as you update your schema in the same way (as > that PR) you should see no issues in upgrading to DSpace 7.x (once that is > available) > > - Tim > > On Sat, Nov 24, 2018 at 5:13 PM Evgeni Dimitrov <dimitr...@gmail.com > <javascript:>> wrote: > >> In 6.2 in the SOLR statistics schema.xml the field id is declared integer >> and the actual content is not integer. >> This causes some queries like this one >> >> q=type:2& >> fq=-isBot:true& >> fq=owningComm:94a589a1-33a0-41e3-a83b-f7644db9a1a5& >> fq=time:[2018-10-01T00:00:00Z+TO+2018-11-01T00:00:00Z]& >> rows=0& >> facet=true& >> facet.limit=-1& >> facet.pivot=id,statistics_type& >> facet.pivot.mincount=1& >> indent=on >> >> to fail. >> >> In a test repository I added a new field >> <field name="idstrng" type="string" indexed="true" stored="true" >> required="false" /> >> and a new copyField >> <copyField source="id" dest="idstrng"/> >> >> Then I ran >> dspace solr-reindex-statistics >> >> Now the above query works with >> facet.pivot=idstrng,statistics_type& >> >> I am getting one facet for every item with subfacets for view events and >> search events. >> >> My only question - before doing this with the production repository - is >> - may this change of the schema cause problems for the upgrade from 6.2 to >> 7.x? >> >> -- >> All messages to this mailing list should adhere to the DuraSpace Code of >> Conduct: https://duraspace.org/about/policies/code-of-conduct/ >> --- >> You received this message because you are subscribed to the Google Groups >> "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to dspace-tech...@googlegroups.com <javascript:>. >> To post to this group, send email to dspac...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/dspace-tech. >> For more options, visit https://groups.google.com/d/optout. >> > -- > Tim Donohue > Technical Lead for DSpace & DSpaceDirect > DuraSpace.org | DSpace.org | DSpaceDirect.org > -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
