TRUNCATE throw a exception (Don't effect index insert data)

[jiamo]

Not a bug . But it may have exception error log.

In example there is trunc data before insert. When pull data it will throw something like

pgsync.exc.ParseLogicalSlotError: 'No match for row: table public.subject, public.book_subject: TRUNCATE: cascade'

[jiamo]

another question is In book example

                            "concat": {
                                "columns": ["publisher_id", "publisher_name"],
                                "into": "xyz"
                            },

seem don't have effect. The created index in es don't have column xyz.

And I don't see code related TRANSFORM_TYPES in constants.py.

[toluaina]

Not a bug . But it may have exception error log.

In example there is trunc data before insert. When pull data it will throw something like

pgsync.exc.ParseLogicalSlotError: 'No match for row: table public.subject, public.book_subject: TRUNCATE: cascade'

Actually. this is a bug. Its means truncate operations are not handled correctly. I will address this

[toluaina]

another question is In book example

                            "concat": {
                                "columns": ["publisher_id", "publisher_name"],
                                "into": "xyz"
                            },

seem don't have effect. The created index in es don't have column xyz.

And I don't see code related TRANSFORM_TYPES in constants.py.

This is still a WIP which is why it is undocumented. The plan is to support concatenation operation with an optional delimiter. I intend to complete this soon.