On 12/18/2014 06:38 PM, Fabrice Jammes wrote:
> My mistake,
>
> Indeed, these params are correct in css but not in cfg files, I have
> removed them for test purpose and to be compliant with original examples.
>
> Andy, it seems the loader doesn't remove css data before reloading
> although I provided "--css-remove" option,
> Shall I remove everything in the db/css using "DROP TABLE" in
> qserv-admin.py, before launching the data-loader?
>
> Thanks,
>
> Fabrice
>
>
> On 12/18/2014 06:26 PM, Fabrice Jammes wrote:
>> It seems it is:
>>
>> Database changed
>> mysql> show tables;
>> +----------------------------------+
>> | Tables_in_qservTest_case01_qserv |
>> +----------------------------------+
>> | Filter |
>> | LeapSeconds |
>> | Logs |
>> | Object |
>> | ObjectFullOverlap_6630 |
>> | ObjectFullOverlap_6631 |
>> | ObjectFullOverlap_6800 |
>> | ObjectFullOverlap_6801 |
>> | ObjectFullOverlap_6968 |
>> | ObjectFullOverlap_6970 |
>> | ObjectFullOverlap_6971 |
>> | ObjectFullOverlap_7138 |
>> | ObjectFullOverlap_7140 |
>> | ObjectFullOverlap_7308 |
>> | ObjectFullOverlap_7478 |
>> | ObjectFullOverlap_7648 |
>> | Object_1234567890 |
>> | Object_6630 |
>> | Object_6631 |
>> | Object_6800 |
>> | Object_6801 |
>> | Object_6968 |
>> | Object_6970 |
>> | Object_6971 |
>> | Object_7138 |
>> | Object_7140 |
>> | Object_7308 |
>> | Object_7310 |
>> | Object_7478 |
>> | Object_7648 |
>> | RefSrcMatch |
>> | Science_Ccd_Exposure |
>> | SimRefObject |
>> | Source |
>> | Source_1234567890 |
>> | Source_6630 |
>> | Source_6631 |
>> | Source_6800 |
>> | Source_6801 |
>> | Source_6968 |
>> | Source_6970 |
>> | Source_6971 |
>> | Source_7138 |
>> | Source_7140 |
>> | Source_7308 |
>> | Source_7310 |
>> | Source_7478 |
>> | Source_7648 |
>> | sdqa_Metric |
>> +----------------------------------+
>> 49 rows in set (0,00 sec)
>>
>>
>> On 12/18/2014 06:20 PM, Serge Monkewitz wrote:
>>> On Dec 18, 2014, at 6:12 PM, Fabrice Jammes
>>> <[log in to unmask]> wrote:
>>>
>>>> DeepSource si a view, shouldn't it be RunDeepSource the director
>>>> table?
>>> In the Winter2013 release, yes it is. But RunDeepSource contains a
>>> bunch of extra columns and uses pipeline column naming conventions,
>>> so I just dumped from the view instead. Note I had to do other
>>> things to make it work in qserv (IIRC I changed the type of BIT
>>> columns to TINYINT). Unless the goal is to duplicate the plain mysql
>>> setup from stripe 82 data as closely as possible, let’s not get hung
>>> up on these details.
>>>
>>>> Furthermore, it seems dirTable and dirColName are optional for now,
>>>> isn't it? Andy doesn't set it in test case01 and 02 and it works.
>>> If you don’t specify them though, the query analysis code will not
>>> let you join between related partitioned tables. Is the data in test
>>> case01/02 being partitioned at all?
>>>
>>> Serge
>>> ########################################################################
>>>
>>> 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
|