-
Notifications
You must be signed in to change notification settings - Fork 2
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
Script keeps looping #20
Comments
Hi @TumGuven Butler Spyglass is going through intensive development right now. I suspect you used v1.0.0? I quickly realised that there were things in that version that did not work well when applied to larger Sense environments. Version 1.1.0 fixed som issues, and with 1.2.0 around the corner (I expect to release it tonight) I hope to have a tool that works also in very large Sense environments. You are right about many vs one lineage file. A more scalable solution was to Finally, regarding the looping - you are once again correct. In version 1.2 there is however a new config option that will enable/disable these automatic extraction runs, making it possible to use Spyglass for one-off extraction runs (that could be scheduled by cron or some other scheduler if needed). |
Additional comment re v1.2: The readme file will be a bit more comprehensive in 1.2, which is a good thing. Finally, you should ALWAYS get the Butler Spyglass tool from the releases page. Anything taken straight from main branch (or some other branch) might be in-development. |
Great! Thank you for your input. I indeed took the files from the main branch. I will wait for the new version to come out. |
@TumGuven 1.2.0 had a bug in it, so go for 1.2.1. The one thing missing is handling of failed extracts. I.e. there are no retries if the tool for some reason gets an error back from Sense, or for some other reason fails extracting data for an app. Closing this ticket for now. |
After I run the script (with node.js) the script keeps repeating itself. it looks like it's in a never ending loop:
Also the files are being stored in seperate csv files instead one single lineage.csv file:
The text was updated successfully, but these errors were encountered: