when migrate data from es to neo4j, an error reported

[ipaste]

Describe the bug
Use the command "./docker/datahub-upgrade/datahub-upgrade.sh -u RestoreIndices" to migrate data from elasticsearch to neo4j, but failed with the below error.

2025-03-28 01:48:48,435 [main] INFO c.l.g.f.entity.EntityServiceFactory:59 - API Requests Throttle Disabled
2025-03-28 01:48:48,906 [main] WARN c.l.r.t.h.client.HttpClientFactory:973 - No scheduled executor is provided to HttpClientFactory, using it's own scheduled executor.
2025-03-28 01:48:48,907 [main] WARN c.l.r.t.h.client.HttpClientFactory:982 - No callback executor is provided to HttpClientFactory, using it's own call back executor.
2025-03-28 01:48:48,907 [main] WARN c.l.r.t.h.client.HttpClientFactory:990 - No Compression executor is provided to HttpClientFactory, using it's own compression executor.
2025-03-28 01:48:48,914 [main] INFO c.l.r.t.h.client.HttpClientFactory:1451 - The service 'null' has been assigned to the ChannelPoolManager with key 'noSpecifiedNamePrefix 1138266797 ', http.protocolVersion=HTTP_1_1, usePipelineV2=false, requestTimeout=10000ms, streamingTimeout=-1ms
WARN [AnnotationConfigApplicationContext] Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'upgradeCli': Unsatisfied dependency expressed through field 'noCodeCleanup': Error creating bean with name 'graphService' defined in class path resource [com/linkedin/gms/factory/common/Neo4jGraphServiceFactory.class]: Unsatisfied dependency expressed through method 'getInstance' parameter 0: Error creating bean with name 'systemOperationContext' defined in class path resource [com/linkedin/gms/factory/context/SystemOperationContextFactory.class]: Unsatisfied dependency expressed through method 'restliSystemOperationContext' parameter 5: Error creating bean with name 'graphService': Requested bean is currently in creation: Is there an unresolvable circular reference?
2025-03-28 01:48:49,554 [main] INFO c.l.r.t.h.c.c.AbstractNettyClient:249 - Shutdown requested
2025-03-28 01:48:49,554 [main] INFO c.l.r.t.h.c.c.AbstractNettyClient:252 - Shutting down
2025-03-28 01:48:49,559 [main] INFO c.l.r.t.h.c.c.ChannelPoolManagerImpl:152 - Shutting down 0 connection pools
2025-03-28 01:48:49,561 [main] INFO c.l.r.t.h.c.c.ChannelPoolManagerImpl:162 - All connection pools shutdown
2025-03-28 01:48:49,562 [main] INFO c.l.r.t.h.c.c.ChannelPoolManagerImpl:119 - All connection pools shut down, closing all channels
2025-03-28 01:48:49,572 [R2 Nio Event Loop-1-1] INFO c.l.r.t.h.c.c.ChannelPoolManagerImpl:103 - Shutdown complete
2025-03-28 01:48:49,572 [main] INFO c.l.r.t.h.c.c.ChannelPoolManagerImpl:152 - Shutting down 0 connection pools
2025-03-28 01:48:49,573 [main] INFO c.l.r.t.h.c.c.ChannelPoolManagerImpl:162 - All connection pools shutdown
2025-03-28 01:48:49,573 [main] INFO c.l.r.t.h.c.c.ChannelPoolManagerImpl:119 - All connection pools shut down, closing all channels
2025-03-28 01:48:49,575 [R2 Nio Event Loop-1-2] INFO c.l.r.t.h.c.c.ChannelPoolManagerImpl:103 - Shutdown complete
2025-03-28 01:48:49,575 [main] INFO c.l.r.t.h.c.c.AbstractNettyClient:249 - Shutdown requested
2025-03-28 01:48:49,576 [main] INFO c.l.r.t.h.c.c.AbstractNettyClient:252 - Shutting down
2025-03-28 01:48:49,576 [main] INFO c.l.r.t.h.c.c.ChannelPoolManagerImpl:152 - Shutting down 0 connection pools
2025-03-28 01:48:49,576 [main] INFO c.l.r.t.h.c.c.ChannelPoolManagerImpl:162 - All connection pools shutdown
2025-03-28 01:48:49,576 [main] INFO c.l.r.t.h.c.c.ChannelPoolManagerImpl:119 - All connection pools shut down, closing all channels
2025-03-28 01:48:49,576 [main] INFO c.l.r.t.h.c.c.ChannelPoolManagerImpl:152 - Shutting down 0 connection pools
2025-03-28 01:48:49,576 [main] INFO c.l.r.t.h.c.c.ChannelPoolManagerImpl:162 - All connection pools shutdown
2025-03-28 01:48:49,576 [main] INFO c.l.r.t.h.c.c.ChannelPoolManagerImpl:119 - All connection pools shut down, closing all channels
2025-03-28 01:48:49,577 [R2 Nio Event Loop-1-3] INFO c.l.r.t.h.c.c.ChannelPoolManagerImpl:103 - Shutdown complete
2025-03-28 01:48:49,578 [R2 Nio Event Loop-1-4] INFO c.l.r.t.h.c.c.ChannelPoolManagerImpl:103 - Shutdown complete
2025-03-28 01:48:49,578 [main] INFO o.a.k.clients.producer.KafkaProducer:1182 - [Producer clientId=producer-1] Closing the Kafka producer with timeoutMillis = 9223372036854775807 ms.
2025-03-28 01:48:49,578 [main] INFO o.a.k.clients.producer.KafkaProducer:1182 - [Producer clientId=producer-1] Closing the Kafka producer with timeoutMillis = 9223372036854775807 ms.
2025-03-28 01:48:49,600 [main] INFO io.ebean.datasource:122 - DataSource [gmsEbeanDatabaseConfig] shutdown min[2] max[50] free[2] busy[0] waiting[0] highWaterMark[1] waitCount[0] hitCount[2] meanAcquireNanos[15341] maxAcquireMicros[23] psc[hit:0 miss:0 put:0 rem:0]
ERROR [LoggingFailureAnalysisReporter]

---

APPLICATION FAILED TO START

---

Description:

The dependencies of some of the beans in the application context form a cycle:

upgradeCli (field private com.linkedin.datahub.upgrade.nocodecleanup.NoCodeCleanupUpgrade com.linkedin.datahub.upgrade.UpgradeCli.noCodeCleanup)
┌─────┐
| graphService defined in class path resource [com/linkedin/gms/factory/common/Neo4jGraphServiceFactory.class]
↑ ↓
| systemOperationContext defined in class path resource [com/linkedin/gms/factory/context/SystemOperationContextFactory.class]
└─────┘

Action:

Despite circular references being allowed, the dependency cycle between beans could not be broken. Update your application to remove the dependency cycle.

[FrankSYLi]

Mmet same issue when execute command below,
...\datahub-1.0.0\docker\datahub-upgrade>docker run --env-file .\env\docker.env --network="datahub_network" acryldata/datahub-upgrade:head -u RestoreIndices
actually, seems "./docker/datahub-upgrade/datahub-upgrade.sh -u RestoreIndices" is going to execute command above.
I guess we would have same issue when doing data migration from neo4j to ES, it should be a bug, pls help to fix it, thanks.
Version info: 1.0.0-rc3