The comparator is optional, so we need to have some kind of default behavior anyway. But I'm sure that it will not work in many cases, because user can't even control the order of fields used for comparison.
On Mon, Feb 29, 2016 at 10:06 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > Why can’t we simply compare the binary arrays? > > On Mon, Feb 29, 2016 at 9:18 PM, Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > > > Igniters, > > > > We currently have a pretty serious limitation for binary objects: they > can > > be used as SQL fields and can't be indexed, because we don't know how to > > compare them. And it seems to me that it can be easily fixed by adding an > > optional comparator to BinaryConfiguration and BinaryTypeConfiguration: > > > > public void setComparator(Comparator<BinaryObject> comparator) > > > > Are there any pitfalls that I'm missing? > > > > -Val > > >
