Tolu Aina

If you remove a column from your schema, you should probably perform a full re-index because the underlying structure of your Elasticsearch has changed and ES is quite particular about...

Hoping to close this if you feel its been addressed.

Closing as resolved. Please feel free to reopen if you feel otherwise,

Yes those slots are created and used by pgsync. they are created when you run the bootstrap command. if you no longer wish to use a configured schema you can...

I think the issue here is that that `ubicacion` Geo field is not a native Postgres field and you need to cast it to a JSON type in order to...

taking a look at this PR thanks

Hi, Sorry for the delay. This has been addressed in the main branch. Can you try this out, please?

- I think it's hard to tell why the index is so large from the data above. - there is some denormalization happening when you go from relational to Elastic/OpenSearch...

Yes, I agree with the comment above. It would be non-trivial to generalize for this use case. Maybe consider indexing the data and using transformations to manipulate the data in...

Sorry about the delay here. Self-referential relationships are NOT supported. There is a WIP to address this but it's not quite finished yet. [This](https://github.com/toluaina/pgsync/blob/main/examples/node/schema.json) is the example of the WIP...