In experimenting with uploading Sightglass data to an ElasticSearch
database, I found the following two changes to be helpful:
adding the datetime of HEAD to .build-info: in order to sort
engines by date, we need to record the date of the commit used to
build the engine. This change retrieves the ISO8601 date using git
and stores it in .build-info's _COMMIT_DATETIME field.
making the fingerprint ID consistent: this change makes the id field
consistent for all of the fingerprinted data--a <name>-<hash> pair
that uniquely identifies the record. This allows us to check if an
engine record, e.g., has already been inserted for the particular
build information it contains.
In experimenting with uploading Sightglass data to an ElasticSearch database, I found the following two changes to be helpful:
HEAD
to.build-info
: in order to sort engines by date, we need to record the date of the commit used to build the engine. This change retrieves the ISO8601 date usinggit
and stores it in.build-info
's_COMMIT_DATETIME
field.id
field consistent for all of the fingerprinted data--a<name>-<hash>
pair that uniquely identifies the record. This allows us to check if an engine record, e.g., has already been inserted for the particular build information it contains.