-
Notifications
You must be signed in to change notification settings - Fork 20
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
Team, and Space filtering #143
Comments
@Nevsksar thanks for the issue! Glad you're using the tap, sorry it isn't quite working for you. Adding filters for workspaces, teams, etc is pretty straight forward. For example we could add something like https://github.com/AutoIDM/tap-indeed/blob/main/tap_indeedsponsoredjobs/streams.py#L80-L87 I'd just propose that the configuration names be something like
Questions I have for you
|
Apologies for the late response I am new to much of this. Regarding number 1 question: the pipeline would last for more thancouple hours and would sometimes fail due to an issue on a workspace or list being read. Thats because my API key has access to 5 workspaces and one of these workspace in an enterprise one so it has dozens of spaces , hundreds of lists and thousands of tasks to be fetch. As per number 2. On these I have two issues: |
Added comments to the PR you're going to need to resubmit that as I can't accept the code in that format https://github.com/AutoIDM/tap-indeed/pull/35/files see this PR for the example I referenced above |
I've been actively testing the ClickUp Tap for the past few days and have identified some opportunities for improvement, particularly for users managing large ClickUp environments with multiple workspaces. Some users, including ClickUp Managers for their companies, have access to numerous workspaces, resulting in access to hundreds of spaces, lists, folders, and projects. Currently, the tap, as it is now, retrieves data from all accessible workspaces when configured via the API key, which overloads the extraction process.
Enhancements Possibilities:
1 - Configurable Workspace Filtering: It would be highly beneficial to add a feature that allows users to configure which specific workspaces (team_ids) the tap should fetch data from. This customization would enable users to focus on extracting data only from the workspaces that are relevant to them.
2 - Custom Data Filtering: Additionally, incorporating the ability to configure which spaces, lists, folders, and projects to fetch data from would be great. These parameters are already available in ClickUp's API and could be integrated into the tap, some of these parameters are already hardcoded into
streams.py
. Inspiration for this feature can be drawn from the Airbyte variant, which supports custom data filtering.I'm attempting a workaround by hardcoding some settings in the
streams.py
file and filtering downstream. However, due to the volume of spaces I have access to, this approach is inefficient and resource-intensive since it fetches all data before applying any filtering. Unfortunatelly my coding skills are null, otherwise I would develop these changes myself instead of trying to set up workarounds.The text was updated successfully, but these errors were encountered: