ServiceX 2.1

This version of servicex is deisgned to work with the RC3 backend of ServiceX.

• Uses the new RC3 API tokens
• Uses the minio secured endpoints supported by RC3
• Supports both xAOD and uproot backends, and includes ways of including other types of backends in the future.
• Use ignore_cache to ignore the local cache
• Uses default image configured with ServiceX - and records that image locally in the cache for reproducibility possibilities.

ServiceX 2.1b4

This is really a RC - we think this is the final set

• Uses API tokens to work with ServiceX
• Defaults to no image name - which means that you end up using the default in ServiceX
• Add ignore_cache to allow one to ignore the current cache when submitting a query.

ServiceX 2.1b3 - Bug Fixes

• Do not close the root file when we load a lazy array from it. The LazyArray requires things to be open.

ServiceX 2.1b2 - Bug Fixes

A few bug fixes:

• Default developer end-points should work if there is no .servicex file present
• Combining files from the uproot backend to awkward arrays should now work.

ServiceX front end package 2.1b1 release

Support multiple types of ServiceX backends implicitly

• The two types, xAOD and uproot are both supported in the sense they can return different types of data (root or parquet files)
• As long as you tell servicex what sort of file to expect, it can render the data into awkward arrays or pandas.DataFrame's.
• The interface and .servicex file have been update to support this, and also behave sensibly if the user doesn't specify anything.

Compatibility with ServiceX:

• Authentication framework will work only up to RC2
• Job submission, etc., should work accross most (all?) versions of ServiceX

ServiceX 3.0 Beta 1 - Removed

• Allow for a "type" of backend when we create the ServiceXDataset
• Allow for multiple servicex backends to be specified in a .servicex file

This breaks the current user interface:

• You have to specify a type of backend when you create the ServiceXDataset
• If you use a .servicex file, you'll need to change the format so you can have multiple servicex endpoints in there.

While this release was built, and it does contain changes, we decided to back out the changes that broke the old UW - so we can go back to the 2.1 series.

ServiceX 2.0.1

This bumps the qastle version number to 2.0.1

ServiceX 2.1 Auto-push Test

This time on the right branch!

ServiceX 2.1 Auto-push Test

This is a bogus release and is identical to 2.0!

ServiceX 2.0.0

Version 2.0 release

• Works with ServiceX RC2 (will also work with RC1, but move to RC2!)
• Supports caching on the local system
• Big re-work of the API
• Brings back errors from ServiceX (DID bad, C++ fails, etc.)
• Substantial internal code rework to enable modularity and testing