Skip to Content

Data Hub Cleanup and keep ALL my publishing errors?

I want to use DH cleanup so we don't get timeout errors and long target publication times but i dont want to loose my publication errors in big batch loads?

Example: keep all error on /datahub-webapp/v1/target-system-publications/<>/errors?pageNumber=0&pageSize=990

Product team what is the suggestion?

Add a comment
10|10000 characters needed characters exceeded

  • also is this message ok:

     2016-04-08 12:59:24,938 [DEBUG] [c.z.h.p.PoolUtilities] Closing connection oracle.jdbc.driver.T4CConnection@3f5be696
     2016-04-08 12:59:27,999 [DEBUG] [HikariPool] Connection returned to pool kernel is broken or evicted.  Closing connection.
     2016-04-08 12:59:27,999 [DEBUG] [c.z.h.p.PoolUtilities] Closing connection oracle.jdbc.driver.T4CConnection@1903223c
    
    

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Apr 07, 2016 at 11:16 PM

    That's an interesting one. You can certainly add a custom cleanup extension which is described here : https://wiki.hybris.com/display/release5/Automated+Elimination+of+Data+Hub+Auditing+Related+Database+Records+-+5.7#AutomatedEliminationofDataHubAuditingRelatedDatabaseRecords-5.7-CreatingaCustomExtensiontoRemoveAuditingRelatedDataRecords. This custom cleanup extension could override the default PublishedItemCleanupService and remove the same entities as the original PublishedItemCleanupService, except for the PublicationError entities. The trick would then be that you need to set the canonicalitempublicationstatus column of all of these PublicationError rows to null to prevent the possibility of entity not found exceptions. These publication errors are what the api you referenced in your quest queries for and returns. I haven't tried this solution out, but it looks like it probably should work from a quick glance through the code. Give it a shot, and post your results here!

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.