manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <>
Subject Re: Solr Output Connector - Questions
Date Thu, 05 Jun 2014 13:20:49 GMT
Hi Piergiorgio,

I had a back-and-forth with Eric Hatcher about this issue about a year
ago.  Solr technically accepts only a limited set of characters, and SolrJ
is therefore not well coded to deal with anything much out of the
ordinary.  I tried to get them to consider removing the url encoding, but
they said no for that reason: "you are doing things which you shouldn't be
doing anyway".

We did work around this problem for field *values*.  I'll review what was
done to see if can be applied to field *names* too.  In the meantime,
please open a ticket to track the issue.


On Thu, Jun 5, 2014 at 9:13 AM, Piergiorgio Lucidi <>

> Hi guys,
> I'm wondering if it is possible to disable the URL encoding on fields on
> this connector.
> Trying to create indexes from a repository that have the name of the field
> with a URI similar to the following:
> {}store_identifier
> But the field is stored in Solr in this way:
> http_3a_2f_2fwww_alfresco_org_2fmodel_2fsystem_2f1_0_7dstore_identifier
> That is bad, our customer needs to create a copyField to solve this issue.
> Is there a reason why we continue to use the URL encoding?
> I saw in the code that it seems to be an issue related to SolrJ, but do you
> think that we can find a workaround for this?
> Thank you.
> Cheers,
> Piergiorgio
> --
> Piergiorgio Lucidi
> Open Source ECM Specialist

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message