You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oodt.apache.org by B W <b....@gmail.com> on 2012/01/15 17:33:14 UTC
Re:Query-CAS thread
What are the circumstances for which CAS becomes is involved in a Query?
When the Query includes observation events that have been registered with
CAS in some time frame in the past?
Re: Query-CAS thread
Posted by B W <b....@gmail.com>.
On Jan 16, 2012, at 9:07 AM, "Mattmann, Chris A (388J)"
<ch...@jpl.nasa.gov> wrote:
> Hi BW,
>
> On Jan 15, 2012, at 10:44 PM, B W wrote:
>>>
>>> But, what predicates the use of CAS over a Profile Service?
>
> Read only versus Read/Write. Profile Servers, Product Servers,
> Query Services, and the like are information integration components
> that federate distributed, virtual data systems. They don't put any
> data back in. CAS not only reads from underlying data sources,
> and queries them, but it writes back into them too.
Ok. Thx.
So, would a primary use of CAS be workflow staging to productize a
product to a new level or subset?
What about replicating?
>
>>
>> So, if the query is first injected in a web-grid Profile Service?
>
> Not always, depends on how you entered the system, some folks
> go to CAS directly.
>
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
Re: Query-CAS thread
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi BW,
On Jan 15, 2012, at 10:44 PM, B W wrote:
>>
>> But, what predicates the use of CAS over a Profile Service?
Read only versus Read/Write. Profile Servers, Product Servers,
Query Services, and the like are information integration components
that federate distributed, virtual data systems. They don't put any
data back in. CAS not only reads from underlying data sources,
and queries them, but it writes back into them too.
>
> So, if the query is first injected in a web-grid Profile Service?
Not always, depends on how you entered the system, some folks
go to CAS directly.
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: Query-CAS thread
Posted by B W <b....@gmail.com>.
On Sun, Jan 15, 2012 at 11:06 AM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:
> Hi BW,
>
> On Jan 15, 2012, at 8:33 AM, B W wrote:
>
> > What are the circumstances for which CAS becomes is involved in a Query?
>
> Typically CAS is queried by any of the following use cases:
>
> 1. An operator/user is searching for data to download, browse metadata
> for, etc.
> They typically do this through our web applications (CAS Browser, CAS
> Curator,
> OPSUI, etc.).
>
> But, what predicates the use of CAS over a Profile Service?
So, if the query is first injected in a web-grid Profile Service?
2. In an automated fashion, the CAS PGE task wrapper queries the File
> Manager
> portion of CAS to determine files to stage, deliver, and their associated
> metadata.
>
> 3. By the Push Pull system and by the Crawler to determine Product
> uniqueness.
>
> ...and some others.
>
> >
> > When the Query includes observation events that have been registered with
> > CAS in some time frame in the past?
>
> That's one of the use cases, yes, per the above.
>
> Cheers,
> Chris
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
Re: Query-CAS thread
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi BW,
On Jan 15, 2012, at 8:33 AM, B W wrote:
> What are the circumstances for which CAS becomes is involved in a Query?
Typically CAS is queried by any of the following use cases:
1. An operator/user is searching for data to download, browse metadata for, etc.
They typically do this through our web applications (CAS Browser, CAS Curator,
OPSUI, etc.).
2. In an automated fashion, the CAS PGE task wrapper queries the File Manager
portion of CAS to determine files to stage, deliver, and their associated metadata.
3. By the Push Pull system and by the Crawler to determine Product uniqueness.
...and some others.
>
> When the Query includes observation events that have been registered with
> CAS in some time frame in the past?
That's one of the use cases, yes, per the above.
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++