On 10/21/2012 03:36 PM, Simon Grinberg wrote: > > ----- Original Message ----- >> > From: "Michael Pasternak" <[email protected]> >> > To: "engine-devel" <[email protected]> >> > Sent: Sunday, October 21, 2012 12:26:46 PM >> > Subject: [Engine-devel] alias in disk instead of name >> > >> > >> > The problem we caused by using alias in disk instead of name is break >> > of search-by-name paradigm >> > in engine.search dialect, not sure why we do not want forcing disk >> > name to be unique [1], >> > but lack of "name" in disk search is does not look good in my view. >> > >> > thoughts? >> > >> > [1] can be easily achieved via appropriate can-do-action >> > verification. > Names by definition are not unique IDs,
they do, otherwise /search wasn't effective, remember users not exposed to entity id, all entities fetched by-name, so names has to be unique. > thus it should not be enforced. > What would be the auto naming conversion to ensure uniqueness with plain text? not sure i follow, i'll assume you refer here to empty name, - you cannot have an entity with no name. > Would you change these on import/export? would you mind elaborating on this? > And so on... > > You should treat the name as a tag/alias that if you bothered to update, > probably means something to you, if not then you don't care anyhow and will > not search by it anyhow. So it's up to the user what to assign. simon, we do not have any /name today in disk, you see it in api for backward compatibility, actually it's emulated over /alias, and the problem is when want to search by-name, it's not included in backend search. > > > -- Michael Pasternak RedHat, ENG-Virtualization R&D _______________________________________________ Engine-devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/engine-devel
