sasdbr.sas runs unmodified on Jenner — test bundle - #1
Open
jenner-analytics wants to merge 1 commit into
Open
Conversation
Adapted the getdatafromdatabricks macro's PROC IMPORT landing step (SAS-DBR-Custom-Integration/sasdbr.sas) into a self-contained bundle that runs against a small mock CSV shaped like the macro's own example call. Ships the shell runner (run_jenner.sh) and its README only.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jenneranalytics.com provides an API that runs SAS code, with support for more than 200 SAS procedures. You can also use it with AI assistants in a collaborative workspace. It's available for Mac on the Apple App Store, and by license for Windows and Linux.
We support the larger community by
(1) increasing access to SAS-compatible systems,
(2) by providing test coverage and a test coverage framework to public SAS repos in order to encourage the use of best practices in software engineering.
Your sasdbr.sas runs on Jenner unmodified — this PR adds a small compatibility bundle so you can see for yourself. It's the test we wrote for your integration accelerator, shared in case it's useful, and was assembled with AI assistance as is most code in modern businesses today.
getdatafromdatabricksis a nicely self-contained piece of design: the macro brackets a whole extract-transfer-land cycle (kick off the DBR job, polllife_cycle_stateuntilTERMINATED, gunzip the payload, thenPROC IMPORTit straight into the caller's library/table) behind four parameters, so the calling code at the bottom reads almost like a one-liner. That's a clean shape for something that's actually doing SSH, HTTP polling, and file decompression under the hood.jenner-check/holds one bundle exercising the macro's landing step — theLIBNAME+PROC IMPORT+PROC PRINT/PROC MEANSsequence, run against a small mock CSV shaped like the macro's own example call (test.drakon4, fromselect * from default.sales_history;). Nothing outsidejenner-check/is touched, nothing executes on merge, and there are no workflow files or hooks.Check out this PR's branch and run from the repo root to try it yourself:
Or
cd jenner-check && ./run_jenner.sh --allto re-run every bundle and verify it against the pinned results. The hosted API is free to try, no signup required — full reference: the docs.The runner uploads only the SAS source text of the script it runs (plus the two-line autoexec) to
api.jenneranalytics.com, where it runs and returns the log and listing. It does not read or upload any data files, so anything sitting next to a script — including your own DBR credentials or connection strings — stays on your machine; nothing is sent unless you run a command yourself. As with pasting a snippet into any hosted tool, only the code you run is transmitted.Merge, close, or ignore this PR — no response expected either way, and we won't open further PRs in this repo. To opt out for good, mention
no-more-prsin any comment here, or open an issue titledjenner-check: opt out.Lawrence W. Sinclair
CEO / Jenner Analytics Ltd
linkedin.com/in/lwsinclair/