Bug 836776

Summary:	ovirt-engine-backend: search engine : inconsistency in fields names
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Oded Ramraz <oramraz>
Component:	ovirt-engine	Assignee:	Alexey Chub <achub>
Status:	CLOSED WONTFIX	QA Contact:	Oded Ramraz <oramraz>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.1.0	CC:	bazulay, dyasny, iheim, lpeer, mkenneth, Rhev-m-bugs, sgrinber, yeylon, ykaul, yzaslavs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	infra
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-16 12:55:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Oded Ramraz 2012-07-01 08:35:37 UTC

Description of problem:

Search engine : There is inconsistency for objects entities fields names , especially for fields which consists of multiple words:

For example:

Mixed : VM : cpu_usage , loggedinuser , datacenter , network_usage 
Without underscore : Template : creationdate , childcount 
Only underscore: allow_snapshot , disk_type 


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Oded Ramraz 2012-07-01 08:37:19 UTC

Only underscores are for new objects such as Volumes and Disks

Comment 2 Itamar Heim 2012-07-01 10:29:05 UTC

miki - please decide on convention.
we can fix all to new convention for auto complete, but will need to make sure we support those changed in syntax for backward compatibility

Comment 3 Itamar Heim 2012-07-01 19:57:30 UTC

note that for new fields in 3.1 we don't have to preserve backward compatibility if we change them.

Comment 4 Miki Kenneth 2012-07-09 11:36:20 UTC

I would go with no underscore.

Comment 5 Eli Mesika 2012-07-24 00:20:04 UTC

(In reply to comment #4)
> I would go with no underscore.

What about Uppercase/Lowercase

in other words:

allow_snapshot for example :

1) AllowSnapshot
2) allowsnapshot
3) allowSnapshot

What should we choose for that ?

Comment 7 RHEL Program Management 2012-08-16 12:55:34 UTC

Quality Engineering Management has reviewed and declined this request.
You may appeal this decision by reopening this request.