[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #HIQ-639816]: Question about pqinsert

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #HIQ-639816]: Question about pqinsert
  • Date: Sun, 25 Jul 2021 16:18:53 -0600
Hi Gilbert,

> I got a message from someone I know, and he writes:
> 
> "I successfully got our NCEP fiber feed working in EDEX. Only issue is that
> it requires me to decompress the product with a PIPE so the only way to get
> LDM to process it is with a pqinsert and a EXP FILE -edex action, so the
> file actually gets written twice. It would be nice if either 1) pqinsert
> supported STDIN or 2) the FILE action supported some sort of flag that told
> LDM to not write if the file exists."
> 
> Does either of this already happened in the LDM that I am not aware about?

No.

pqinsert(1) doesn't support reading from standard input because it needs to 
know the size of the file in order to create an LDM data-product. It can get 
this information from the operating system for a regular file, but not from 
standard input without reading all of standard input into a temporary file. It 
would then have to read the file back in to create the data-product.

The "don't overwrite an existing file" is an interesting concept. I don't see 
it's connection with the use-case you outlined, however. Can you describe that 
use-case in more detail?

--Steve

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: HIQ-639816
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.