From solr-user-return-146357-archive-asf-public=cust-asf.ponee.io@lucene.apache.org Wed Feb 13 13:29:44 2019 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 5F589180674 for ; Wed, 13 Feb 2019 14:29:44 +0100 (CET) Received: (qmail 13292 invoked by uid 500); 13 Feb 2019 13:29:42 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 13255 invoked by uid 99); 13 Feb 2019 13:29:41 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Feb 2019 13:29:41 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id D27D218188A for ; Wed, 13 Feb 2019 13:29:40 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.2 X-Spam-Level: X-Spam-Status: No, score=-0.2 tagged_above=-999 required=6.31 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id yLAAAJ_9UyU1 for ; Wed, 13 Feb 2019 13:29:39 +0000 (UTC) Received: from mail-wr1-f41.google.com (mail-wr1-f41.google.com [209.85.221.41]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 027BB5F543 for ; Wed, 13 Feb 2019 13:29:39 +0000 (UTC) Received: by mail-wr1-f41.google.com with SMTP id x10so2474721wrs.8 for ; Wed, 13 Feb 2019 05:29:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:date:subject:message-id :references:in-reply-to:to; bh=ZBFJV5V9nohTtgZ3DiL5U6ZGpNxAtggN79cdH1kySLg=; b=q32h1cbgUzRhK3HLWjB6mP7+qOeFv50bCZeIy612VxT3QwAcrD44zu6t/Atjk6mnN6 JKQ3OPAheMq54Z85kwcPHQfvwzMht4vuv/lPCCT1FZL0Fyy8/ohicUGRCeXCJOYbsWjE /JynFbNrDQdXBKO0mgUwZwwgOq9nTASu2dDgUw9bQ5eFWk6s/RyUtb60cu2kS7KOkFlO bp6f5qYQZOvFqvnyalUfXiYcNzyUDhHj7vuaTJsc+AfREizmjFuiW5HkGhg5uMuIg15E KChxKcLbiYUKyQHIZdAG2L3G3AS3VgiiGFDB0lBwcAExJ2CSgze6LZ3dSrrjas+indD+ AKig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version:date :subject:message-id:references:in-reply-to:to; bh=ZBFJV5V9nohTtgZ3DiL5U6ZGpNxAtggN79cdH1kySLg=; b=UKksvSG017JUx3dpZhFLhT5K+etIfpIueFFhqaubX+Adh8BzHlYKFPluBpgRVwemdT hu261ohCJAU6UCctI07BBhw8nkZMa6v98JaDCHJ1QJYFHl3tq51Z49q6as4m28xML7az JkIaGEZK5G3rxILJSskHTmsDKG4aEdTuqyJtfNjPppRdFNu30xoivp0bdOW2MTQew+pG nRxD7zoS/uWVAn5YvRBKhqtgswZiQxw5tf6iAkrQOlBNam6ymfb9IiT10t4QjJ43agkZ bqKUa9YUdDRGlcFnllCKOMLz/VjnkH9uik2PpStnLsu/Rlq7nUR2t9w1MnGWZWBR8ndC hbcg== X-Gm-Message-State: AHQUAuaw8xVQp3O5PfyBSZESfo+VZidfZCykv6ARwNO0YU6ruRZ4IxkW HcNk+zK4GpWGMjWbnNgRSerG4ETF X-Google-Smtp-Source: AHgI3IbKhu1b/kU+dzLLyoPDs8MQuNZMQcl1oxD83eXm0ktU09FMgXBVbkOcsWAwnC0hxjC9mxksGw== X-Received: by 2002:adf:b68a:: with SMTP id j10mr452723wre.224.1550064578190; Wed, 13 Feb 2019 05:29:38 -0800 (PST) Received: from ?IPv6:2a01:598:888f:bdd0:1057:ba99:e2dc:3464? ([2a01:598:888f:bdd0:1057:ba99:e2dc:3464]) by smtp.gmail.com with ESMTPSA id z5sm3863120wmi.15.2019.02.13.05.29.37 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Feb 2019 05:29:37 -0800 (PST) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable From: =?utf-8?Q?J=C3=B6rn_Franke?= Mime-Version: 1.0 (1.0) Date: Wed, 13 Feb 2019 14:02:48 +0100 Subject: Re: SOLR and AWS comprehend Message-Id: References: In-Reply-To: To: solr-user@lucene.apache.org X-Mailer: iPhone Mail (16D57) I guess you have to find out which product fits better your needs. The use c= ase can be somehow reflected in both solutions, but the description about th= e use case is very generic so difficult to say. > Am 13.02.2019 um 13:17 schrieb Gareth Baxendale : >=20 > This is perhaps more or an architecture question than dev code but > appreciate collective thoughts! >=20 > We are using Solr to order records and to categorise them to allow users t= o > search and find specific medical conditions. We have an opportunity to mak= e > use of Machine Learning to aid and improve the results. AWS Comprehend is > the product we are looking at but there is a question over whether one > should replace the other as they would compete or if in fact both should > work together to provide the solution we are after. >=20 > Appreciate any insights people have. >=20 > Thanks Gareth >=20 > --=20 > Confidential information may be contained in this message.If you are not=20= > the intended recipient, any reading, printing, storage, disclosure, copyin= g=20 > or any other action taken in respect of this e-mail is prohibited and may=20= > be unlawful. If you are not the intended recipient, please notify the=20 > sender immediately by using the reply function and then permanently delete= =20 > what you have received.