Bug 724851

Summary:	copyTrans should not be invoked when doing the first push.
Product:	[Retired] Zanata	Reporter:	Ding-Yi Chen <dchen>
Component:	Component-Persistence	Assignee:	zanata-dev-internal <zanata-dev-internal>
Status:	CLOSED NOTABUG	QA Contact:	Ding-Yi Chen <dchen>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.3-alpha-1	CC:	sflaniga, zanata-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-01-27 02:13:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Ding-Yi Chen 2011-07-22 01:19:11 UTC

Description of problem:
When push the content of a new project, the copyTrans is not needed.

However, copyTrans was invoked even for the initial push. Consequently, the pushing is very slow.


Version-Release number of selected component (if applicable):
1.4-SNAPSHOT (20110722-0601)

How reproducible:
Always

Steps to Reproduce:
1. Prepare a new project, say, anaconda, http://git.fedorahosted.org/git/?p=anaconda.git
2. Start pushing anaconda
3. From server side, monitor the output of server log.
  
Actual results:
copyTrans was invoked.

Expected results:
copyTrans should be suppress for initial run.

Comment 1 Sean Flanigan 2011-09-07 04:32:42 UTC

Assigning to Scrum product owner for prioritisation.

Comment 2 Sean Flanigan 2012-01-27 02:13:11 UTC

The current implementation of copyTrans copies suitable translations from any matching document, across all projects and versions.

Thus, even in a new project, it is possible to find matches, especially if the document has been pushed to a different project at some point.

You can disable the copyTrans feature when pushing like this:
  mvn zanata:push -Dzanata.copyTrans=false
for Maven, or 
  zanata push --no-copytrans" 
for Python.