Re:Launch HN: Hydra (YC W22) – Query any database via Postgres
by sdesol on Wednesday February 23, 2022 @03:22PM
(#30445895)
I've never heard of Calcite before and dug a bit deeper into this project and found it to be quite active. Only taking into consideration changes to Java files, this is the repo activity for the last 12 months:
[ Parent
| on HN ]
Re:Launch HN: Hydra (YC W22) – Query any database via Postgres
by michaelmior on Thursday February 24, 2022 @06:38AM
(#30453597)
The community is also great. Honestly, the main thing preventing things from moving faster is lack of time to review PRs. There's a lot of interesting things in the pipe!
Re:Launch HN: Hydra (YC W22) – Query any database via Postgres
by sdesol on Thursday February 24, 2022 @11:05AM
(#30456297)
Yeah I can see what you mean. There are currently 20 open pull requests [1] that hasn't changed in over 28 days, which accounts for 53% of all open pulls that are less than 4 months old.
1) https://oss.gitsense.com/insights/github?q=pull-age%3A%3C%3D...
Re:Launch HN: Hydra (YC W22) – Query any database via Postgres
by riverdroid on Wednesday February 23, 2022 @04:53PM
(#30447040)
What do you use to produce this analysis?
Re:Launch HN: Hydra (YC W22) – Query any database via Postgres
by sdesol on Wednesday February 23, 2022 @05:39PM
(#30447578)
My product (https://gitsense.com) moves most of Git's history into a Postgres database and from there, you can execute the following SQL statement:
select
commit_ym AS month,
count(distinct(author_email)) as authors,
count(distinct(commit_id)) as commits,
count(distinct(path_id)) as files,
sum(total) as churn
from
z1_commits_422 as commits,
z1_changes_422 as changes,
z1_code_churn_422 as churn
where
commits.id=changes.commit_id and
changes.code_churn_id=churn.id and
lang='java'
group by commit_ym
order by commit_ym desc
limit 12
By having most of Git's history in SQL, I can slice, dice and cross-reference code history, which is how my product works.