Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data error when changing the type of a document #51

Open
yregaieg opened this issue Nov 6, 2017 · 3 comments
Open

Data error when changing the type of a document #51

yregaieg opened this issue Nov 6, 2017 · 3 comments
Labels

Comments

@yregaieg
Copy link
Collaborator

yregaieg commented Nov 6, 2017

Following a type input error, I had to change a document type back to cm:content (form custom:document), I was able to do this on the alfresco side, without issues. AAAR extraction on the other hand did not catch the change and still shows the document in question as of the specific type (custom:content).

@fcorti, is this a bug or an intentional behavior ?

@fcorti fcorti added the question label Nov 6, 2017
@fcorti
Copy link
Owner

fcorti commented Nov 6, 2017

So, we are talking about one document in particular.
Are you extracting the custom:document type in AAAR?
If yes, it should be extracted and updated.
If not, the behaviour you describe is correct.

@yregaieg
Copy link
Collaborator Author

yregaieg commented Nov 6, 2017

I am extracting both cm:content and custom:document.
Obviously custom:document is a child type of cm:content


The user made an input mistake specifying a bunch of documents (6) as custom:document. And since the way back (from specific to more generic types) is not supported in Alfresco OOTB, I had to patch the node using some scripting.
I just realized (6days after that) that I have no errors in the logs, and the documents in question did not change at all in datamart (they still carry the old modification timestamp). And I had to set them right manually in the DB to set things right, so I am guessing there is definitely something wrong with the extraction logic (unless going from specific to generic types is not supported in AAAR as well)

@fcorti
Copy link
Owner

fcorti commented Nov 6, 2017

Yes, under this scenario it should be extracted by the ETL.
It's time for a debug.
Let me know if I can help in debugging it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants