Will Johnson

@DanW985 - Not sure if you're still looking for an answer here but, yes, this does come with the 2.1 API. You can start hitting it with `http://localhost:21000/api/atlas/v2` if you...

Hi, @sbbagal13 Thank you for using PyApacheAtlas! Can you share which version of PyApaceAtlas you're on? The traceback is in a surprising spot. It's like it couldn't find any of...

Oh yikes, @sbbagal13 - I might batch this up into a few things and take advantage of the AtlasObjectId feature. You can see more about this feature [here](https://datasmackdown.com/oss/pyapacheatlas/excel/bulk-upload.html#referencing-entities-not-being-uploaded-with-atlasobjectid) I'd follow...

Closing this for now (due to > 1 month since last update) but @sbbagal13 please feel free to reopen if you are still having an issue.

Hi, @edobrynin-dodo Thank you for using PyApacheAtlas! This error means that you have a reference to a guid "-1002" (which was definitely generated by the GuidTracker) in your upload but...

Closing out due to no follow up but please feel free to reopen if you are still having the same issue after looking at the above suggestion.

Hi, @EdoMatt ! Thank you for using PyApacheAtlas. This looks to be a server side issue unfortunately. Have you considered using the export option instead? https://wjohnson.github.io/pyapacheatlas-docs/latest/pyapacheatlas.core.html#pyapacheatlas.core.client.PurviewClient.export_terms The only challenge with...

Closed, over 30 days with no follow up.

Hmm.. This is something specific to the requests package and your network setup. You can try following the steps in #191 to requests requests_verify = False on your Purview Client...

> WRONG_VERSION_NUMBER Try this out? https://stackoverflow.com/questions/65516325/ssl-wrong-version-number-on-python-request When creating the PurviewClient pass in `requests_verify=False` and `requests_proxies=proxies` after defining what proxies you are using.