Ticket #983 (closed Defect: fixed)

Opened 8 years ago

Last modified 8 years ago

topic in declarative migration not in DB after successfull installation

Reported by: Malte Owned by:
Priority: Critical Milestone: Release 4.8.1
Component: DeepaMehta Standard Distribution Version: 4.8
Keywords: Cc: jri
Complexity: 3 Area: Application Framework / API
Module: deepamehta-core

Description

I have made a very strange observation as i was installing the dm4-kiezatlas-etl module into a new database with dm 4.8.1-SNAPSHOT. 

"topics": [ ..
        {
            "value":    "Rummelsburger Bucht",
            "uri":      "ka2.bezirksregion.li-rummelsburger-bucht",
            "type_uri": "ka2.bezirksregion"
        },
        {
            "value":    "Berlin",
            "uri":      "ka2.city.berlin",
            "type_uri": "dm4.contacts.city"
        },
        {
            "value":    "Deutschland",
            "uri":      "ka2.country.deutschland",
            "type_uri": "dm4.contacts.country"
        }
]

After successfull installation of this migration, a topic with URI "ka2.country.deutschland" is in my DB but a topic with the URI "ka2.city.berlin" is not. I deemed this impossible and retried it now several times - and when doing a "cold start" with the dm4-kiezatlas-etl module it is the case. I am running this on the latest SNAPSHOT 4f0e76a6bdaeec664cb34fdde8335dd02babb424 ("dm4-storage-neo4j: deal with non-DM nodes (#911).")

Do you have any idea how this could happen or what might has changed that this could happen?

Change History

comment:1 Changed 8 years ago by Malte

Sorry, all clear. OMG, of course i deleted the topic in a later migration.

comment:2 Changed 8 years ago by Malte

  • Status changed from new to closed
  • Resolution set to fixed

comment:3 Changed 8 years ago by jri

No problem.

General trac hint: consider closing tickets with "worksforme" in case nothing was actually fixed.

Note: See TracTickets for help on using tickets.