Importar manteniendo los IDs de publicaciones antiguas en Discourse

Soporte Migración
1

Estoy a mitad de camino en una migración desde Kunena; he ejecutado (casi) con éxito una migración de prueba, pero al pensar en el problema de los permalinks y también en el de los enlaces internos, me pregunto…

¿Sería difícil que Discourse cree los nuevos posts manteniendo los IDs de los posts antiguos que Kunena asignó originalmente? Hay ventajas obvias en este enfoque.

Supongo que esto implicaría:

  1. Algunos ajustes en el script de importación. ¿Alguien puede estimar qué tan “profunda” sería esta modificación? ¿Se asigna el ID del post muy profundamente en el código de Discourse o en algún lugar del script base de importación?

  2. Una forma de evitar que Discourse asigne IDs de posts ya utilizados a nuevos posts en el futuro. ¿Existe algún lugar donde podamos configurar Discourse para que comience a asignar IDs de posts desde 100.000 en adelante, por ejemplo?

  3. ¿Pueden los IDs de los posts ser no numéricos? De ser así, pensé que “k12345” (para contenido proveniente de Kunena) podría ser una buena solución intermedia. Mantendría una forma de referenciar los IDs de los posts antiguos, pero no entrarían en conflicto con los nuevos IDs asignados por Discourse.

¡Gracias de antemano por cualquier orientación!

2

The import script saves the import id in a post custom field. You can use it to create permalinks. Several importers do that. You can look at others for examples.

3

Thanks Jay, I know that, and I use that to go from old ids to new ids.

But it would be more practical to simply use the same number and avoid that de-referencing. I am doing parts of my import with SQL and it complicates queries.

Also, the permalinks table can get quite huge. A regexp redirect is better, and easy if the id is constant.

4

The permalinks table is only as big as the post table. You know about permalink normalizations?

But to answer your question, yes, having discourse use different topic id would be very hard.

5

It seems Discourse relies on PostgreSQL to assign the id, which is numeric:

image

And it seems PostgreSQL allows manipulation of that “sequence object”:

https://www.postgresql.org/docs/8.3/static/functions-sequence.html

So I guess my number 2 is answered “yes” and my number 3 is answered “no”. My question number 1 is probably what you mean by “very hard”, right? :frowning:

EDIT: let me just add that posts uses the same mechanism as topics

6

I had heard about these regexp operations but I was thinking they required post ids to match so a simple find-and-replace could take me from the old post id to the new one.

Or is the mechanism more intelligent and it does a lookup on the post custom field to translate ids?

7

Yes. You still need to have the post (or topic or category) ID in a permalink.

Your solution might work with a plugin that you would have to continually maintain, but it’ll be really hard, and the recommended way works and has been used dozens of times, including several with millions of posts, and that’s just me.

8

The approach (without keeping a plug in all the time) could be:

  1. Disable automatic serial numbers for topics
  2. Import everything with the old ids
  3. Re-enable serials, starting at a number larger than the MAX currently used

But ok, I get the point - it’s easier with the permalinks feature. I have found many posts with specific questions about this, mostly people trying to get their regexps right, but I haven’t found any page documenting the actual mechanism in general… is there such a page?

As always, thanks a lot for your help.

9

Can anybody point to any Documentation on how to use the permalinks feature? Even if it’s minimal docs. I don’t mind helping to write a more extended documentation once I understand how this works. Thanks.

10

The best thing to do is to grep Permalink script/import-scripts/*rb and look at how people have used it.