Skip to content
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.

Explore the possibility of migrating to TiDB #44

Open
1 task done
Rustin170506 opened this issue May 19, 2021 · 3 comments
Open
1 task done

Explore the possibility of migrating to TiDB #44

Rustin170506 opened this issue May 19, 2021 · 3 comments
Labels
lifecycle/rotten type/feature Categorizes issue or PR as related to a new feature.

Comments

@Rustin170506
Copy link
Contributor

Feature Request

  • I have searched the issues of this repository and believe that this is not a duplicate.

Is your feature request related to a Issue or PR(Optional)

None.

Describe the feature you'd like:

We can probably migrate devstats to TiDB.

We need to investigate what is incompatible and unsupported and find solutions.

Do you have any ideas on how to implement it?(Optional)

@Rustin170506 Rustin170506 added the type/feature Categorizes issue or PR as related to a new feature. label May 19, 2021
@Mini256
Copy link
Member

Mini256 commented May 19, 2021

pgsql supports the percentile_disc function that used to return the first input value whose position in the ordering equals or exceeds the specified fraction.

TiDB supports the PERCENT_RANK() windows function, but there does not seem to be a function called PERCENT_VALUE() for now.

Related SQL:

select
  'open2merge;All;p15,med,p85' as name,
  percentile_disc(0.15) within group (order by open_to_merge asc) as open_to_merge_15_percentile,
  percentile_disc(0.5) within group (order by open_to_merge asc) as open_to_merge_median,
  percentile_disc(0.85) within group (order by open_to_merge asc) as open_to_merge_85_percentile
from
  tdiffs

@ti-chi-bot
Copy link
Member

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-community-infra or Mini256.
/lifecycle stale

@ti-chi-bot
Copy link
Member

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-community-infra or Mini256.
/lifecycle rotten

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/rotten type/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants