Changes between Version 8 and Version 9 of MOPSPartitioning


Ignore:
Timestamp:
08/17/2010 03:11:28 PM (9 years ago)
Author:
jbecla
Comment:

faint->forced source

Legend:

Unmodified
Added
Removed
Modified
  • MOPSPartitioning

    v8 v9  
    1212=== Separating mops tables to simplify partitioning ===  
    1313 
    14 To provision for the fact that some !DiaSources/Sources/!FaintSources/!FaintDiaSource will be linked to objects, and some to moving objects, current scheme is: 
     14To provision for the fact that some !DiaSources/Sources/!ForcedSources/!ForcedDiaSource will be linked to objects, and some to moving objects, current scheme is: 
    1515 * Source, !DiaSource tables: there are 2 columns in each of these tables: objectId and movingObjectId. Typically, only one of these ids would be set. 
    16  * Faint* tables are going to be handled through 4 separate tables: !FaintSourceForObject, !FaintDiaSourceForObject, !FaintSourceForMovingObject, !FaintDiaSourceForMovingObject 
     16 * Forced* tables are going to be handled through 4 separate tables: !ForcedSourceForObject, !ForcedDiaSourceForObject, !ForcedSourceForMovingObject, !ForcedDiaSourceForMovingObject 
    1717 
    1818Disadvantage of keeping together Sources and !DiaSources that belong both to objects and moving objects is that whatever partitioning scheme we chose for Sources/Objects, the !MovingObject table will be forced to use that scheme too (this is required in order to avoid cross-node communication during joins).