data-migration | 用于数据迁移、缓存预热，springboot架构。支持数据区间分割、动态调整线程池配置、任务进度实时查看等特性 | Data Migration library

Should anyone get the same error in the future, here is what we were told by the AWS tech specialist:

There is a known (to AWS) issue with the pglogical plugin. The solution requires using the test_decoding plugin instead.

1. Enforce using the test_decoding plugin on the DMS Endpoint by specifying pluginName=test_decoding in Extra Connection Attributes
2. Create a new DMS task using this endpoint (using the old task may cause it to fail due to dissynchronization between the task and the logs)

It sure did resolve the issue, but we still don't know what the problem really was with the plugin that is strongly suggested everywhere in the DMS documentation (at the moment).

You need to set Xdebug's xdebug.client_host to the IP address of your IDE, which you indicated is 192.168.1.150.

You also need to turn off xdebug.discover_client_host, as that would try to use the internal Docker network IP (172.100.0.2), which is not where your IDE is listening on.

Remember: Xdebug makes a connection to the IDE, not the other way around.

The article linked to in the documentation is quite old and has since been superseded by Django's own support for data migrations, which is documented here.

The Django documentation for these does a decent job of explaining what they are and how to create them, so assuming that you've read that, then this is the sort of thing that is being suggested in the tutorial:

1. Create a data migration in one of your project's apps:

Since you're adding browser objects to node's global, you also need to add the Node object like so:

that is a very good question, as there is in deed a very big difference.

If you import a model, you will get whatever is currently defined in your model code. But what happens if you want to remove a model? How do you make sure your migration will still work?

That's why there is apps.get_model. It will give you a "virtual" Model based on state defined by the previous migrations. Note that this is not the same as the Model in your code. It does not have any of the custom functions and behaviors you implemented unless they are part of the ORM API. In other words mostly fields and meta options like ordering and co.

Please also note that the correct signature is apps not app_registry. It should not be confused with the app registry in django.apps.apps. It has a get_model method too. This one however will return the model in your current code.

I know it can be all a bit confusing at first (and even later). I would suggest following a simple rule. Do not import any of your own code into a migration. Backport behavior into the migration, if you must.

I hope that distinction helps you a bit. Please leave me a comment if you have further questions. I am happy to extend my answer.

Best -Joe

I can't test UpdateDatabaseWithDbUp@2 but I have sth what explain how you can achieve your goal. First define templeate.yaml

Can you help me how to do this in Data Factory

According to your description,it seems you have trouble with export data,not import data. You could use Copy activity in ADF which supports cosmos db connector.For you needs,cosmos db is source dataset and please add one more sink dataset(destination). Such as some json files in the blob storage.Just make sure you configure right authentication information with your cosmos db account.

ADF is more suitable for the batch back up or daily back up.

or any steps just to manual backup cosmos DB

Yes,Storage Explorer is not for exporting data from cosmos db,Data migration tool is the suitable option.Please install the tool and refer to some details from this link:https://docs.microsoft.com/en-us/azure/cosmos-db/import-data#export-to-json-file

DMT is more suitable for single back up.Surely,it also supports execution in the batch if you use command line to execute it.

After going through my AppDelegate file many times, I found that I was doing a Core Data save operation in the applicationDidBecomeActive method which is also called when the app starts from a suspended state.

So if my Core Data stack setup closure didn't finish before the applicationDidBecomeActive is called the app would crash.

After removing it, the app was working fine without any crashes

Since Spring-Boot 1.2.4 you can disable logging with properties (Github issue) :