seems like we DO transfer replicas

[vvo]

Looking at the README, for transferindex it says:

Replica indices and settings not transferred.

While I just used the command and replicas were created too. What's the real state?

[sepehrfakour]

Hey @vvo , good catch. The docs should be updated. When transferring an index, we do a getSettings on the source and setSettings on the destination, which will include the replicas setting.

What we don't do is forward settings or synonyms to replicas.

[Meschreiber]

Customer XXX just ran into this issue as well -- will add the functionality soon!

[Meschreiber]

something along these lines

    const replicas = settings.replicas;
    replicas.forEach(replica => {
        const sourceReplicaIndex = sourceClient.initIndex(replica);
        const destReplicaIndex = destClient.initIndex(replica);
        sourceReplicaIndex.getSettings().then(settings => {
            destReplicaIndex.setSettings({ranking: settings.ranking}, (err, content) => {
                    if (err) throw err;
                    console.log(content);
        })
    })

[sepehrfakour]

@Meschreiber were you thinking of doing something like adding an optional flag to the transferindex command so the user can specify if they want to forward settings/synonyms to replicas? Let me know if I can help in any way! :)

[sepehrfakour]

Readme has been updated in the meantime. Will publish new release soon.

[sepehrfakour]

4.0.3 published.

[sepehrfakour]

As of 4.0.6, both TransferIndex and TransferIndexConfig commands now each have optional -e <true|false> flag to exclude replicas from settings object when transferring index or index settings! 🎉

cc @vvo @Meschreiber

[vvo]

thanks!