-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking issue for the MetricEngine #2070
Labels
Milestone
Comments
2 tasks
This was referenced Nov 2, 2023
This was referenced Nov 10, 2023
This was referenced Nov 17, 2023
This was referenced Dec 15, 2023
2 tasks
3 tasks
Is the TODO list above updated? Perhaps we can create subtasks issue for each task so that we can keep the status synced. Take https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists as the reference. |
From now on, we need to keep compatibility with older versions as possible as we can. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What type of enhancement is this?
Performance
What does the enhancement do?
RFC metric-engine proposes a new region engine
Metric
. Here is the tracking issue for implementing it.Related progress is also tracked in GitHub Project https://github.com/orgs/GreptimeTeam/projects/34
public
schema.GreptimeDatabase
service into two different servicesRegionEngine
andRegionServer
feat: define region server and related requests #2160MetricEngine
on top ofMitoEngine
MetadataRegion
to handle operations to metadata feat: Metric engine skeleton #2687DataRegion
to handle operations to data feat: create logical region to metric engine #2706Create
request feat: implement create region request for metric engine #2694Write
request feat: write logical region to metric engine #2759Read
request feat: handle scan request on metric engine #2793Alter
request feat: alter logical region in metric region #2726MetricEngine
Implementation challenges
No response
The text was updated successfully, but these errors were encountered: