Builds fail using wrong branch of impala-lzo

An earlier build succeeded using this commit from the branch 'master' 

commit dccb1be88a5e237b06ae69cd99b048a38d9f024b (HEAD -> master)
Author: Philip Zeyliger <philip@cloudera.com>
AuthorDate: Tue Jan 22 14:21:42 2019 -0800
Commit: Philip Zeyliger <philip@cloudera.com>
CommitDate: Fri Feb 1 11:04:06 2019 -0800

Adapt to new interface for AddDiskIoRange (IMPALA-7980)

The change for IMPALA-7980 moves out the "are we done
adding disk io ranges" accounting from AddDiskIoRange()
to a new UpdateRemainingScanRangeSubmissions call.

but now the build is failing pointing at 'origin/master:

commit 9543908ec82245878c4060dec64a1533d7adbee6 (origin/master-backup-2019-01-23, origin/master)
Author: Alex Behm <alex.behm@cloudera.com>
AuthorDate: Thu Dec 4 16:53:06 2014 -0800
Commit: Alex Behm <alex.behm@cloudera.com>
CommitDate: Fri Dec 5 14:28:25 2014 -0800

Remove data compaction flag.

Change-Id: Ife72c7ee630b6ecd9024a3d33b7673b56fcf1fba

which is obviously something pretty old and wrong