-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
feat(ingest/unity): Use ThreadPoolExecutor for CLL #8952
feat(ingest/unity): Use ThreadPoolExecutor for CLL #8952
Conversation
2ab5b9e
to
a4df8dc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
broadly seems reasonable
assuming the tests are unchanged here, right
@@ -45,6 +46,8 @@ | |||
|
|||
logger: logging.Logger = logging.getLogger(__name__) | |||
|
|||
MAX_WORKERS = 100 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this looks unused?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch, was using this before I added the config param
We really need to add some databricks connector tests, if it's to be a high-ish priority source. There's some unit tests but their coverage is not great |
a4df8dc
to
37b207b
Compare
Checklist