Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-1756

Create human-readable spec of default/required/optional parameters for db/table creation

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: Qserv
    • Labels:
      None
    • Team:
      Data Access and Database

      Description

      Hey, we need a spec for db and table parameters, okay? This should be on paper rather than having bits of it scattered in our collective heads.

      Let's put it in docs/source/schema.rst, okay?

        Attachments

          Issue Links

            Activity

            Hide
            jammes Fabrice Jammes added a comment -

            Good idea Daniel Wang [X],

            On my side I would like to have no default values for dirTable and dirColName in cfg files. This fields imply that the table is a "child" table, so having default value for them can be ambiguous.
            Furthermore it seems that Object/ObjectId names, which are current default in loader, won't be used in most of our future cases.

            Maybe also we should have a nice and easy to remmeber/understand vocabulary for director/child, (like for example parent/child, maestro/musician, guide/follower, leader/follower, mentor/pupil, or principal/subordinate, ...). Indeed, in my understanding of english child and director aren't related, isn't it?

            One other point, it seems that part.id and dirColName both relate to FK of director table. If yes, maybe we should unify these two fields in cfg files?

            Thanks,

            Fabrice

            Show
            jammes Fabrice Jammes added a comment - Good idea Daniel Wang [X] , On my side I would like to have no default values for dirTable and dirColName in cfg files. This fields imply that the table is a "child" table, so having default value for them can be ambiguous. Furthermore it seems that Object/ObjectId names, which are current default in loader, won't be used in most of our future cases. Maybe also we should have a nice and easy to remmeber/understand vocabulary for director/child, (like for example parent/child, maestro/musician, guide/follower, leader/follower, mentor/pupil, or principal/subordinate, ...). Indeed, in my understanding of english child and director aren't related, isn't it? One other point, it seems that part.id and dirColName both relate to FK of director table. If yes, maybe we should unify these two fields in cfg files? Thanks, Fabrice
            Hide
            jbecla Jacek Becla added a comment -

            Daniel, this has been "in progress" for a long time. Should we switch back to "todo", or close, or perhaps it is done?

            Show
            jbecla Jacek Becla added a comment - Daniel, this has been "in progress" for a long time. Should we switch back to "todo", or close, or perhaps it is done?
            Hide
            fritzm Fritz Mueller added a comment -

            Table parameters are covered in ingest system documentation.

            Show
            fritzm Fritz Mueller added a comment - Table parameters are covered in ingest system documentation.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              fritzm Fritz Mueller
              Watchers:
              Fabrice Jammes, Fritz Mueller
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.