Mailing-List: contact dev-help@oodt.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@oodt.apache.org
Received-SPF: pass (nike.apache.org: domain of chris.a.mattmann@jpl.nasa.gov
 designates 128.149.139.106 as permitted sender)
From: "Mattmann, Chris A (3980)" <chris.a.mattmann@jpl.nasa.gov>
To: "dev@oodt.apache.org" <dev@oodt.apache.org>
Subject: Re: trunk filemgr busted
Thread-Topic: trunk filemgr busted
Thread-Index: Ac+SI0jYl0l/Q1c0TA+5KLpo0IPPSAAwc2sA///7YIA=
Date: Sat, 28 Jun 2014 15:08:16 +0000
Message-ID: <CFD42799.165C66%chris.a.mattmann@jpl.nasa.gov>
References: <3C566CBB-A031-48C9-8A94-FF3A28B7858D@jpl.nasa.gov>
 <CAGaRif15CSiwJHOkTv2yX3TVgSC8D_fW+QkjWWJfYv7CqBpyzg@mail.gmail.com>
In-Reply-To: 
 <CAGaRif15CSiwJHOkTv2yX3TVgSC8D_fW+QkjWWJfYv7CqBpyzg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.4.2.140509
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3D4C95AACB5DBF40BEB77C8E50A4F8DB@ad.jpl>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hey Lewis,

Sorry I should have been more specific. I'll file a JIRA issue about
this too, here's the scenario:

On DARPA XDATA, I built a new RADIX-based system for processing an
employment dataset using 0.7-radix (trunk). I then created a set of
policy for the File Manager for employment datasets containing ~4
product types, etc. I then tried to start file manager. It was up and
running, but would keep giving me NPEs when trying to get ProductTypes
(look them up), and then wouldn't ingest, etc.

I took the *exact same policy* (after trying to debug RADIX for a day
which nicely swallows *all file manager output and doesn't print errors*)
and ran it against an 0.6 filemgr, which properly loaded the policy (which
I eyeballed over and over and over again trying to find something wrong
with
it, but couldn't) fine and I moved on. So there seems to be something in
0.7 filemgr that wouldn't read my policy correctly and I was wondering if
it had to do with the updates you were making (maybe it didn't).

One thing I did wonder though is that does the trunk filemgr still produce
a tgz when running mvn install? It didn't seem to anymore for me and if it
doesn't (per the test updates) that should be fixed/reverted since we need
to produce a tgz on mvn install (so those get published to the Central
repo).
Are you seeing this too?

Cheers,
Chris


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.mattmann@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


-----Original Message-----
From: Lewis John Mcgibbney <lewis.mcgibbney@gmail.com>
Reply-To: "dev@oodt.apache.org" <dev@oodt.apache.org>
Date: Saturday, June 28, 2014 1:24 AM
To: "dev@oodt.apache.org" <dev@oodt.apache.org>
Subject: Re: trunk filemgr busted

>Chris,
>What is wrong?
>Are you referring to tests only?
>I am aware that filemgr is broken w.r.t tests right now.
>I am actively working on this as we speak e.g. 1.24am on Saturday
>morning... WOW I love Apache OODT.
>Lets try and pull this together.
>Lewis
>
>
>On Fri, Jun 27, 2014 at 9:17 AM, Mattmann, Chris A (3980) <
>chris.a.mattmann@jpl.nasa.gov> wrote:
>
>> Hey guys the trunk filemgr is busted / Lewis any idea what is up?
>>
>> Cheers,
>> Chris
>>
>> Sent from my iPhone
>>
>
>
>
>--=20
>*Lewis*