Print

Print


And... I am starting to realize that DM-1038 is blocking
DM-1703 (because we need to scan list of active queries
before I can proceed with deleting a table)


On 04/10/2015 12:28 PM, Jacek Becla wrote:
> Andy
>
> There is something wrong with stories for DM-1703
> (db/table mgmt) and DM-1038 (managing queries). (It
> is my fault!). I want to clean it, but I'd like to
> run it by you before doing it.
>
> 1038, which is about managing *queries* has
>   - 1396 - implement db/table deletion
>   - plus two stories which do make sense
>
> 1396 should NOT be part of 1038. It belongs to 1703.
> And..  I think 1703 covers table deletion, but it is
> missing database deletion story. Right?
>
> So, I am thinking about moving 1396 (which is 20 SP,
> pretty heavy) from 1038 to 1396, and calling it
> "Implement database deletion". I guess I'd split it
> into two: "Design CSS schema to support db deletion",
> and "Implement distributed database deletion".
>
> What do you think? Am I missing something?
>
> Jacek
>
> ########################################################################
> 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