You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Greetings! We have been looking at using neo4j apoc extensions as a potential replacement for traditional ETL tools such as SSIS etc. The JSON and XML procedures offer a lot of potential to make this a reality. However, for us to be able to fully replace something like an SSIS, we would need to be able to have some way to monitor the progress of a job, and have alerts or some way of taking action in the event of an ETL job failure. Ideally as well it would be great if a job could be broken up into smaller transactional boundaries to prevent memory pressure issues, and increase recoverability should a job fail at a given step.
We are definitely enjoying working with the APOC extensions you have made thus far - very powerful!!!
Thanks! M..
The text was updated successfully, but these errors were encountered:
Issue by mimomenome
Tuesday Mar 07, 2017 at 21:21 GMT
Originally opened as neo4j-contrib/neo4j-apoc-procedures#306
Greetings! We have been looking at using neo4j apoc extensions as a potential replacement for traditional ETL tools such as SSIS etc. The JSON and XML procedures offer a lot of potential to make this a reality. However, for us to be able to fully replace something like an SSIS, we would need to be able to have some way to monitor the progress of a job, and have alerts or some way of taking action in the event of an ETL job failure. Ideally as well it would be great if a job could be broken up into smaller transactional boundaries to prevent memory pressure issues, and increase recoverability should a job fail at a given step.
We are definitely enjoying working with the APOC extensions you have made thus far - very powerful!!!
Thanks! M..
The text was updated successfully, but these errors were encountered: