[ 
https://issues.apache.org/jira/browse/CONNECTORS-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412778#comment-13412778
 ] 

Karl Wright commented on CONNECTORS-470:
----------------------------------------

bq. two attributes ows_Author="1073741823;#System Account" and 
ows_Editor="1073741823;#System Account" starts with some prefix other than 
ows_ProgId="29;#". This yields 'multiple values encountered for non multiValued 
field author:' solr error.

I think that should be considered a Solr connector bug.  The entire field 
should be considered the one (single) metadata value.  I'll open a separate 
ticket.

As far as special casing those two fields, I am not comfortable with it.  I 
wish I knew what kind of substitution SharePoint was expecting clients to do on 
such strings, so that we could do it as a general procedure.

bq. some attributes are exactly same with ProgId, after progIDSubstitute() they 
become empty string too. For example : ows_ParentLeafName="29;#" and 
ows__CheckinComment="29;#"

That's fine, unless you have reason to believe there should be a non-empty 
checkin comment for this document.


                
> SharePoint 2010 support
> -----------------------
>
>                 Key: CONNECTORS-470
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-470
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: SharePoint connector
>    Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 0.7
>
>         Attachments: CONNECTORS-470.patch, CONNECTORS-470.patch, 
> CONNECTORS-470.patch, CONNECTORS-470.patch, Screen Shot 2012-05-31 at 
> 11.21.12 AM.png, getFieldNames.jpg, pagination.zip, pom.patch, pom.patch
>
>
> See here for list of the SharePoint web services for SharePoint 2010:
> http://msdn.microsoft.com/en-us/library/ee705814.aspx

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to