Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 48C23200CBE for ; Thu, 22 Jun 2017 23:56:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 47849160BD3; Thu, 22 Jun 2017 21:56:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 888D0160BE7 for ; Thu, 22 Jun 2017 23:56:05 +0200 (CEST) Received: (qmail 57269 invoked by uid 500); 22 Jun 2017 21:56:04 -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 57176 invoked by uid 99); 22 Jun 2017 21:56:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jun 2017 21:56:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 0BD4B1A08E3 for ; Thu, 22 Jun 2017 21:56:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -98.702 X-Spam-Level: X-Spam-Status: No, score=-98.702 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_NUMSUBJECT=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 860qgGflIqXk for ; Thu, 22 Jun 2017 21:56:03 +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 475945FC43 for ; Thu, 22 Jun 2017 21:56:02 +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 E5F77E0D55 for ; Thu, 22 Jun 2017 21:56: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 3C4BB21DD5 for ; Thu, 22 Jun 2017 21:56:00 +0000 (UTC) Date: Thu, 22 Jun 2017 21:56:00 +0000 (UTC) From: "Karl Wright (JIRA)" To: dev@manifoldcf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CONNECTORS-1433) Add CLI options to pipeline modules, e.g. allow Tika to export TEXT, not BASE64 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 22 Jun 2017 21:56:06 -0000 [ https://issues.apache.org/jira/browse/CONNECTORS-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059970#comment-16059970 ] Karl Wright edited comment on CONNECTORS-1433 at 6/22/17 9:55 PM: ------------------------------------------------------------------ In this scenario below, what would the equivalent of the "my_data" field name be in the ES connector? PUT my_index/my_type/my_id?pipeline=attachment {code} { "*+my_data+*": "e1xydGYxXGFuc2kNCkxvcmVtIGlwc3VtIGRvbG9yIHNpdCBhbWV0DQpccGFyIH0=" } {code} GET my_index/my_type/my_id {code} { "found": true, "_index": "my_index", "_type": "my_type", "_id": "my_id", "_version": 1, "_source": { "*+my_data+*": "e1xydGYxXGFuc2kNCkxvcmVtIGlwc3VtIGRvbG9yIHNpdCBhbWV0DQpccGFyIH0=", "attachment": { "content_type": "application/rtf", "language": "ro", "content": "Lorem ipsum dolor sit amet", "content_length": 28 } } } {code} When it PUTs the document, what is the field name? I have this from ElasticSearchIndex.java (line 202): {code} // Since ES 1.0 pw.print(" \"_content\" : \""); Base64 base64 = new Base64(); base64.encodeStream(inputStream, pw); pw.print("\"}"); {code} so I assumed it was the _content field, but that doesn't work in the pipeline. I'll investigate further. was (Author: svanschalkwyk): In this scenario below, what would the equivalent of the "my_data" field name be in the ES connector? PUT my_index/my_type/my_id?pipeline=attachment {code} { "*+my_data+*": "e1xydGYxXGFuc2kNCkxvcmVtIGlwc3VtIGRvbG9yIHNpdCBhbWV0DQpccGFyIH0=" } GET my_index/my_type/my_id { "found": true, "_index": "my_index", "_type": "my_type", "_id": "my_id", "_version": 1, "_source": { "*+my_data+*": "e1xydGYxXGFuc2kNCkxvcmVtIGlwc3VtIGRvbG9yIHNpdCBhbWV0DQpccGFyIH0=", "attachment": { "content_type": "application/rtf", "language": "ro", "content": "Lorem ipsum dolor sit amet", "content_length": 28 } } } {code} When it PUTs the document, what is the field name? I have this from ElasticSearchIndex.java (line 202): {code} // Since ES 1.0 pw.print(" \"_content\" : \""); Base64 base64 = new Base64(); base64.encodeStream(inputStream, pw); pw.print("\"}"); {code} so I assumed it was the _content field, but that doesn't work in the pipeline. I'll investigate further. > Add CLI options to pipeline modules, e.g. allow Tika to export TEXT, not BASE64 > ------------------------------------------------------------------------------- > > Key: CONNECTORS-1433 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1433 > Project: ManifoldCF > Issue Type: Wish > Components: Tika extractor > Reporter: Steph van Schalkwyk > Assignee: Karl Wright > Attachments: CONNECTORS-1433.patch, image.png, image.png > > > Would love to have Tika spout TEXT, not BASE64. -- This message was sent by Atlassian JIRA (v6.4.14#64029)