Good idea, Jacek. I forgot where that link was. We still want a page covering CSS, but it can be on confluence and be free of db/table specifics.
-Daniel
(typed on a small touch screen)
On Jan 9, 2015 9:16 PM, Jacek Becla <[log in to unmask]> wrote:
>
> Daniel,
>
> How about we revisit
>
> https://dev.lsstcorp.org/trac/wiki/db/Qserv/CSS
>
> take what is useful, and retire the rest.
>
> (I know this page does not have the exact answers
> to what you are asking for, but it is somewhat
> relevant)
>
> I'd put the new documentation either somewhere close to
> the code, or in a new confluence page; trac is frozen,
> I believe.
>
> Have a nice weekend,
> Jacek
>
>
>
> On 01/09/2015 07:15 PM, Daniel L. Wang wrote:
> > 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
>
########################################################################
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
|