LISTSERV mailing list manager LISTSERV 16.5

Help for QSERV-L Archives


QSERV-L Archives

QSERV-L Archives


QSERV-L@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

QSERV-L Home

QSERV-L Home

QSERV-L  December 2014

QSERV-L December 2014

Subject:

Re: --keep-input-data option for data-loader

From:

Fabrice Jammes <[log in to unmask]>

Reply-To:

General discussion for qserv (LSST prototype baseline catalog)

Date:

Fri, 19 Dec 2014 16:24:16 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (72 lines)

Hi Andy,

I'm OK with this, DM-1724 created.

Cheers,

Fabrice

On 12/19/2014 04:10 PM, Salnikov, Andrei A. wrote:
> Hi Fabrice,
>
> I can make separate option for unzipped file location but I do not
> think it has to be a required option. There will be cases when people
> load uncompressed data and I don't want them to specify options
> that are not used. Probably we can require it only if there are
> compressed files given as input. Can you open a ticket for it?
>
> Cheers,
> Andy
>
>
> Fabrice Jammes wrote on 2014-12-19:
>> Hi Andy,
>>
>> Maybe chunkDir could be renamed to workDir as it is also used to unzip
>> input data for non partitioned table?
>> If yes, it's documentation could also be updated.
>>
>> Indeed I first thought this directory wasn't used for non partitioned
>> table so I didn't specified it, and its default value was used.
>> Maybe we could also remove its default value (loader_chunks/ in the
>> execution directory) and force the user to specify
>> it? Indeed for now it creates this directory in the execution directory,
>> this is dangerous in case of large amount of data.
>> Imagine a sysadmin/DBA which would launch it on / and fill it.
>>
>> Cheers,
>>
>> Fabrice
>>
>> On 12/19/2014 03:19 PM, Fabrice Jammes wrote:
>>> Hi Andy,
>>>
>>> partitioner derails on w13 input data, that's why I would need a
>>> --keep-input-data option in data-loader, in order to easily test the
>>> partitioner cmd-line.
>>> This is not straightforward to add because input data is unzipped in
>>> chunkDir, so if --keep-chunks option isn't specified input data will
>>> be deleted.
>>> It is of course also deleted if --keep-chunks is specified.
>>>
>>> For now I'll comment the code which remove this directory, but could
>>> you please provide me this option?
>>>
>>> Thanks,
>>>
>>> Fabrice
>>>
>>> ########################################################################
>>> Use REPLY-ALL to reply to list
>>>
>>> To unsubscribe from the QSERV-L list, click the following link:
>>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1
>
>

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2018
February 2018
January 2018
December 2017
August 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use