Skip to content

sasdbr.sas runs unmodified on Jenner — test bundle - #1

Open
jenner-analytics wants to merge 1 commit into
T1A:mainfrom
jenner-analytics:jenner-check/initial-bundles
Open

sasdbr.sas runs unmodified on Jenner — test bundle#1
jenner-analytics wants to merge 1 commit into
T1A:mainfrom
jenner-analytics:jenner-check/initial-bundles

Conversation

@jenner-analytics

Copy link
Copy Markdown

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.

getdatafromdatabricks is a nicely self-contained piece of design: the macro brackets a whole extract-transfer-land cycle (kick off the DBR job, poll life_cycle_state until TERMINATED, gunzip the payload, then PROC IMPORT it 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 — the LIBNAME + PROC IMPORT + PROC PRINT/PROC MEANS sequence, run against a small mock CSV shaped like the macro's own example call (test.drakon4, from select * from default.sales_history;). Nothing outside jenner-check/ is touched, nothing executes on merge, and there are no workflow files or hooks.

jenner-check/
├── README.md
├── run_jenner.sh
└── t001_land_databricks_extract/
    ├── script.sas
    ├── autoexec.sas
    ├── expected.json
    ├── meta.json
    └── expected/
        ├── log.txt
        └── output.txt

Check out this PR's branch and run from the repo root to try it yourself:

gh pr checkout <PR_NUMBER>
curl -sS --data-binary @jenner-check/t001_land_databricks_extract/script.sas https://api.jenneranalytics.com/v1/quick

Or cd jenner-check && ./run_jenner.sh --all to 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-prs in any comment here, or open an issue titled jenner-check: opt out.


Lawrence W. Sinclair
CEO / Jenner Analytics Ltd
linkedin.com/in/lwsinclair/

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant