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  January 2015

QSERV-L January 2015

Subject:

required parameters for table and db creation

From:

"Daniel L. Wang" <[log in to unmask]>

Reply-To:

General discussion for qserv (LSST prototype baseline catalog)

Date:

Fri, 9 Jan 2015 19:15:42 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (46 lines)

Hello,

It seems that we are missing a spec for what parameters are required and 
what are optional and what is default, with regards to specifying 
databases and tables in qserv.

I have some concept of what is required, e.g., you must specify overlap 
for director tables (it should not default to 0 or some k), but it 
occurs to me that perhaps others may disagree, and we have no reference 
doc to point either for users or for us to argue over.

(I am also uncertain how to find docs for the parameters for the 
partitioner, and what they default to, but that's different question.)

I think we need one. This will save us a fair amount of confusion in 
implementation and will clarify the use of qserv-admin.py as well as 
data-loader.py . I've created DM-1756 to track this work. Feel free to 
pick it up as you wish. I will plan on putting in some version that I 
derive from the bits of code that care (I don't think they are all 
consistent... perhaps that is my fault).

Anyway, please let me know if you have any "yes, parameter X needs to be 
required! people need to be explicit about that" or "don't you dare make 
Y required! let's just default to Y=0" kinds of thoughts, and I'll be 
sure to cover them.

I'm asking about "what is required/optional/default from the user", 
which is slightly different than "what we should store in the metadata". 
The former should be strict enough to prevent the user from making 
mistakes and expressive enough to capture the intent, with a bit of "do 
what I mean". The latter is really about capturing enough information so 
that qserv is extremely sure of how it's supposed to operate.

Serge, I'm sure you've thought about what's optional and required for 
partitioning, so if you can point me at your doc or the part of code 
that enforces such things, that would help.

Thanks,
-Daniel

########################################################################
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