Feature Request: fetch runs table with selected fields only
See original GitHub issueIn my project I have 800 runs each of which has 18000 hyperparameters. In result,
project.fetch_runs_table()
takes 51 seconds.
I rarely need all those parameters. Usually, I need just run_ids
or a few selected columns. Maybe you also do not need additional traffic 😉. I wish I had sth like:
project.fetch_runs_table(columns=['sys/run_id', 'node/param1'])
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Retrieve selected fields from a search | Elasticsearch Guide [8.5]
Retrieve specific fieldsedit. The following search request uses the fields parameter to retrieve values for the user.id field, all fields starting with http ......
Read more >fetch() - Web APIs | MDN
The promise resolves to the Response object representing the response to your request. A fetch() promise only rejects when a network error is ......
Read more >Get Specific Columns Using “With()” Function in Laravel ...
Now I want to join these two tables using Eloquent with() but want specific columns from the second table. I know I can...
Read more >Create a simple select query - Microsoft Support
When you open a table, you see all the fields. A query is a handy way to save a selection of fields. Note:...
Read more >Query (Feature Service/Layer)—ArcGIS REST APIs
The definitions for one or more field-based statistics to be calculated. This parameter is supported only on layers/tables that indicate supportsStatistics is ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey @wjaskowski, filtering the results by column names should be available soon. Optimistically within 2 weeks, but may be up to 4 - it’s already in the short dev queue.
At the same time the object from which the pandas dataframe is converted from takes >7GB:
Simply unusable.