From dev-return-18008-archive-asf-public=cust-asf.ponee.io@manifoldcf.apache.org Wed Apr 25 13:36:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id CE6AE180679 for ; Wed, 25 Apr 2018 13:36:04 +0200 (CEST) Received: (qmail 2180 invoked by uid 500); 25 Apr 2018 11:36:03 -0000 Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@manifoldcf.apache.org Delivered-To: mailing list dev@manifoldcf.apache.org Received: (qmail 2169 invoked by uid 99); 25 Apr 2018 11:36:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Apr 2018 11:36:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 607F6C8ED6 for ; Wed, 25 Apr 2018 11:36:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id ayUduoLcGBkG for ; Wed, 25 Apr 2018 11:36:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 81E045F175 for ; Wed, 25 Apr 2018 11:36:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 96388E0047 for ; Wed, 25 Apr 2018 11:36:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 5057D241C6 for ; Wed, 25 Apr 2018 11:36:00 +0000 (UTC) Date: Wed, 25 Apr 2018 11:36:00 +0000 (UTC) From: "Karl Wright (JIRA)" To: dev@manifoldcf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CONNECTORS-1503) UpdateProcessor SolrCloud and ManifoldCF MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CONNECTORS-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452086#comment-16452086 ] Karl Wright commented on CONNECTORS-1503: ----------------------------------------- [~shinichiro abe], you have confirmed that if you set MCF Solr Connection to not use extracting update handler, and you set an argument "processor=", it properly obeys the processor argument? The reason I wonder about this is because the code in HttpPoster for SolrInputDocument does not distinguish between fields and arguments: it uses addField() for both, e.g.: {code} if (contentAttributeName != null) { // Copy the content into a string. This is a bad thing to do, but we have no choice given SolrJ architecture at this time. // We enforce a size limit upstream. Reader r = new InputStreamReader(is, Consts.UTF_8); StringBuilder sb = new StringBuilder((int)length); char[] buffer = new char[65536]; while (true) { int amt = r.read(buffer,0,buffer.length); if (amt == -1) break; sb.append(buffer,0,amt); } outputDoc.addField( contentAttributeName, sb.toString() ); } ... // Write the arguments for ( String name : arguments.keySet() ) { List values = arguments.get( name ); outputDoc.addField( name, values ); } ... {code} I am pretty sure that fields and arguments would need to be handled differently, no? > UpdateProcessor SolrCloud and ManifoldCF > ---------------------------------------- > > Key: CONNECTORS-1503 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1503 > Project: ManifoldCF > Issue Type: Bug > Components: Solr 6.x component > Affects Versions: ManifoldCF 2.9.1 > Environment: SolrCloud 6.6 > ManifoldCF 2.9.1 > Reporter: Maxence SAUNIER > Assignee: Shinichiro Abe > Priority: Major > Attachments: 20170421-1740.png, jira_update_processor.png, manifoldcf_arguments_uniqFields.png, manifoldcf_output_conf.zip > > > Hello, > [Link to Apache mail archive|http://mail-archives.apache.org/mod_mbox/manifoldcf-user/201804.mbox/%3C079e01d3d7da%24807b8f60%248172ae20%24%40citya.com%3E] > When we used Argument option in ManifoldCF for SolrCloud, ManifoldCF add they arguments on the POST request and not on the url parameters. So, for add a (pre)processor or a post-processor with the url, it's not possible. > [SolrConfig updateRequestProcessorChain|https://lucene.apache.org/solr/guide/6_6/config-api.html#ConfigAPI-Whatabout_updateRequestProcessorChain_] > [call UpdateRequestProcessors|https://lucene.apache.org/solr/guide/6_6/update-request-processors.html#UpdateRequestProcessors-Processor_Post-ProcessorRequestParameters] > [Conf image|https://image.ibb.co/cZC8bn/jira_update_processor.png] > Solr response: > org.apache.solr.common.SolrException: ERROR: [doc=file://///srvics01/ways_holding/gestion_ged/gerance/3573/201102081135_ENVOIDEVISPP.doc] unknown field 'processor' -- This message was sent by Atlassian JIRA (v7.6.3#76005)