Return-Path: X-Original-To: apmail-uima-user-archive@www.apache.org Delivered-To: apmail-uima-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AC74A18AF1 for ; Fri, 2 Oct 2015 16:02:05 +0000 (UTC) Received: (qmail 64992 invoked by uid 500); 2 Oct 2015 16:01:49 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 64952 invoked by uid 500); 2 Oct 2015 16:01:49 -0000 Mailing-List: contact user-help@uima.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@uima.apache.org Delivered-To: mailing list user@uima.apache.org Received: (qmail 64938 invoked by uid 99); 2 Oct 2015 16:01:49 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Oct 2015 16:01:49 +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 00E501A07BB for ; Fri, 2 Oct 2015 16:01:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.9 X-Spam-Level: ** X-Spam-Status: No, score=2.9 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id Odb6IUvwF2a6 for ; Fri, 2 Oct 2015 16:01:43 +0000 (UTC) Received: from mail-qk0-f180.google.com (mail-qk0-f180.google.com [209.85.220.180]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 6804B2054A for ; Fri, 2 Oct 2015 16:01:42 +0000 (UTC) Received: by qkap81 with SMTP id p81so44722750qka.2 for ; Fri, 02 Oct 2015 09:01:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=RNGC7nePIOHS5pz72GpKbOzgwhi7bCuUBL9Gn+2XMxk=; b=SAzpURtQ5upWfr/Glcv5PTLmmbp51QeGuBpbnJeDRDKY/B24GiP3ip1N+1xaPo8/5E VpolYStPYptoWfduPuZ2ziWr3Fi+SJOd63oQPyZYQ516175z4Dc07aQE5ZmsgBevdtI0 nXrEiPP5eSyBAVdniz4ZpRkKU3bgSMch2zMrhjn9VWqI6/u7cbsadVQzZ/pzs97Jv8Sy /OtWkZXRKfSpJDg9pK8peIOOq0Q8BDxP9SDPZj2xMLFjT/aTvtcRJ90i4hdHJdUn0me8 VJWX0lHVC8PEX48A6Aah1MdEfGgFNR2Lo2UZIcEMqPq0QfIjNMrbWQny9yPLBH0zQT23 XaJg== X-Received: by 10.55.19.14 with SMTP id d14mr11337800qkh.54.1443801695294; Fri, 02 Oct 2015 09:01:35 -0700 (PDT) MIME-Version: 1.0 References: <560D48D1.4050401@schor.com> In-Reply-To: <560D48D1.4050401@schor.com> From: =?UTF-8?B?Sm9zw6kgVG9tw6FzIEF0cmlh?= Date: Fri, 02 Oct 2015 16:01:25 +0000 Message-ID: Subject: Re: How to correclty implement delta serialization in locally deployed CPE pipeline? To: user@uima.apache.org Content-Type: multipart/alternative; boundary=001a11400e1a2c9a7805212147ae --001a11400e1a2c9a7805212147ae Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Marshall, thanks for your reply. I think I have figured it out: I had not realized the session object saves data under a per-component name space, which prevented the serializer from finding the data saved by the collection reader and deleting it. I'll try an alternative strategy today and come back of I bump into any other issues. Thanks! Jta On Thu, Oct 1, 2015, 10:53 Marshall Schor wrote: > Hi, > > A little more detail of what you're doing may help us figure out what's > happening. > > What API(s) are you using to do the serialization? > > -Marshall > > On 9/29/2015 2:57 PM, Jos=C3=A9 Tom=C3=A1s Atria wrote: > > Hello all, > > > > I've been trying to wrap my head around this for a while, and I can't > seem > > to get it to work. Could someone please explain what is the most > > straightforward way of implementing delta serialization in a local, > > multithreaded CPE pipeline? > > > > So far, I've tried using a collection reader that uses a > > SharedSerializationData that is stored in the current UIMA session, and > > creates a CAS marker that is also stored in a map in the current UIMA > > session under a CAS identifier key, and then using this > > SharedSerializationData oject and the marker retrieved from the UIMA > > session from the CAS identifier to serialize the delta to disk, but thi= s > > procedure causes an OutOfMemory exception if I try to process all of my > > data (Not that much in my opinion, ~2000 CASes). > > > > I assume that I'm missing some basic aspect of the API, but after tryin= g > to > > deal with it for a while I just gave up... > > > > A more specific version, as far as I could understand: Delta > serialization > > requires a SharedSerializationData object and a CAS marker. What is the > > correct way to create, store and retrieve these in a simple, > > multi-threaded, locally deployed CPE processing pipeline? (i.e. No need > to > > support AS or DUCC facilities, etc). > > > > Any help would be greatly appreciated. > > Thanks! > > jta > > > > -- sent from a phone. please excuse terseness and tpyos. enviado desde un tel=C3=A9fono. por favor disculpe la parquedad y los erroe= rs. --001a11400e1a2c9a7805212147ae--