Yeah, but it shouldn't be necessary. The use of "drop 0" is probably
faster than "elastic", but the application I am building will never have
enough records to make performance an issue. 

I know that I have piped unmatched details into an output driver in the
past, so something must make what I am doing in this one really special
:( 

Regards, 
Richard Schuh 

 

> -----Original Message-----
> From: CMSTSO Pipelines Discussion List 
> [mailto:[EMAIL PROTECTED] On Behalf Of Rich Greenberg
> Sent: Friday, January 18, 2008 3:17 PM
> To: [email protected]
> Subject: Re: Oddity
> 
> On: Fri, Jan 18, 2008 at 02:21:50PM -0800,Schuh, Richard Wrote:
> 
> } I have two pipes, below, that are identical in every 
> respect except that } one has a seemingly superfluous stage, 
> "| COPY" inserted prior to the } output. The first writes 
> nothing to the file while the latter pipe does } write. The 
> all. Stem contains 302 entries; only 48 of them match the } 
> exception list, stem except. Both pipes agree in this respect 
> What is } going on here? Why is the copy stage needed before 
> any following stages } can run?
> 
> I am sure that John or Melinda can explain it in detail but 
> in my experience, it helps with timing and dispatching 
> problems.  Replace the COPY with ELASTIC should also work.
> 
> --
> Rich Greenberg  N Ft Myers, FL, USA richgr atsign panix.com  
> + 1 239 543 1353
> Eastern time.  N6LRT  I speak for myself & my dogs only.    
> VM'er since CP-67
> Canines:Val, Red, Shasta & Casey (RIP), Red & Zero, Siberians 
>  Owner:Chinook-L
> Retired at the beach                                     Asst 
> Owner:Sibernet-L
> 

Reply via email to