thingsboard / thingsboard/database-migrator
About changing postgres DB to Cassandra Hybrid
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 10
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
I have previously posted a question about changing postgres DB to Cassandra Hybrid. At that time, it was said that the work could be carried out through the GitHub - thingsboard/database-migrator link, and it proceeded in the way of Scenario #1. After several trials and errors, the file was successfully filed with postgresql.dmp -> migration Folder, moved through the command to the /var/lib/passandra/data/thingsboard folder, and then modified the thingsboard.conf file to boot the thingsboard. However, it was not possible to check the time series data of the terminal on the thingsboard.(If you change it back to the single Postgresql setting, you can see it well) I will attach a picture of the setting. Please answer me.
I used thingsboard version 3.3.4 PE.
As a result of checking the log, the following log was found. You are about to send the log source file together. Can you tell me how to respond?
ERROR o.t.s.d.t.CassandraBaseTimeseriesDao - [DEVICE][01cf3f30-e069-11ec-b067-a1db09533645] Failed to fetch partitions for interval 1664582400000-1664582400000
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Scenario #1 migration steps, postgresql.dmp in the migration folder, the thingsboard.conf settings, and the reported CassandraBaseTimeseriesDao log entry. Reproduce the missing time-series query using ThingsBoard 3.3.4 PE and compare the hybrid configuration with the working PostgreSQL-only configuration. Done means the migrated terminal time-series data is visible without the partition-fetch error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cassandra, java, postgresql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100