Reconciling Commits vs Revisions

[Doug Swartz]

All the eyeql documentation equates a commit to a revision. However when I compare the results of an eyeql query in the form "select revisions where date in [ 2013-01-01, 2013-09-20 ] return count(revisions)" to the Repository statistics screen in Fisheye, eyeql almost always returns a significantly higher number than the commit count shown on the screen.

Since I'm querying for less than the last 12 months of data, I expect the revision count to be less than the commit count shown on the screen. What don't I understand?

[lpater · Accepted solution]

Hi Doug,

a changeset is a set of file revisions. A single revision is a single file modified in the changeset.

So an svn commit with three file changes, will be a single commit or changeset, but three revisions.

See here for some more details: https://confluence.atlassian.com/display/FISHEYE/Glossary#Glossary-Changeset

[Doug Swartz]

Lukasz,

Thank you for the answer. It matches what I might have guessed.

Which leads to the follow-on questions:

1. "Can I query Commits through EyeQL?"
2. "Why does the EyeQL documentation refer to revisions as commits?"

For example, the EyeQL Reference Guide page has an example:

Find commits that do not have comments:
select revisions from dir / where comment = "" group by changeset

[lpater]

1. While the select clauses of EyeQL queries deal with revisions exclusively, you can get some changeset data, using the 'group by' clause and an aggregate column.

Something like this (note that at least one aggregate clause is required for the grouping to take effect):

select revisions from dir "/"
where author = "lukasz pater <lpater@atlassian.com>" 
order by date  desc  
group by changeset 
return csid, comment, date, author, count(revisions)

2. Seems like a documentation bug. I'll try to get it fixed.

[Doug Swartz]

The repositories are Subversion