row.meta.cursor in step always same value when parsing in worker mode
See original GitHub issueNot sure if this is a bug or simply a limitation of parsing in worker mode, but when I parse a (local) file in worker mode, the row.meta.cursor
always points to the end of the file:
Papa.parse(file, {
header: true,
worker: true, // << worker is true
step: (row, parser) => {
console.log(row.meta.cursor, file.size);
// => logs "677403 677403" 8973 times
},
});
Papa.parse(file, {
header: true,
worker: false, // << worker is false
step: (row, parser) => {
console.log(row.meta.cursor, file.size);
// => logs increasisng number upto filesize as expected
},
});
Is there any way to get the cursor (or anything else that can be used as a progress-indicator) when parsing in worker mode?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:8
Top Results From Across the Web
Setting up a Papa Parse progress bar with Web workers
The progress bar is updated, but only after the CSV file is parsed and the site is set up with data, so the...
Read more >Basic Normalization | Airbyte Documentation
When you run your first Airbyte sync without the basic normalization, you'll notice that your data gets written to your destination as one...
Read more >Query Processing Architecture Guide - SQL Server
Row mode execution is a query processing method used with traditional RDBMS ... If only a few rows with specific key values are...
Read more >Browser Test Steps - Datadog Docs
Select any MFA global variables defined in Synthetic Monitoring Settings. This type of global variable stores time-based one time password (TOTP) secret keys, ......
Read more >KeyEvent - Android Developers
getAction() value: multiple duplicate key events have occurred in a row, ... This mask is used to check whether one of the ALT...
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 Free
Top 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
OMG, since 2019, no one has address this issue. Its pretty annoying.
I don’t know if this is the case BUT, I got the cursor progress + worker enable working enabling the chunk option.
The following example was giving me always the same cursor value as described by @sandergarretsen :
Once I enabled the chunk size, it started to work a expected:
The version I am using is 5.0.0, can someone confirm that?