Skip to content
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

CSV Export wrong values #128352

Closed
zacksiri opened this issue Mar 23, 2022 · 6 comments
Closed

CSV Export wrong values #128352

zacksiri opened this issue Mar 23, 2022 · 6 comments
Labels
bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Feature:Reporting:CSV Reporting issues pertaining to CSV file export needs-team Issues missing a team label

Comments

@zacksiri
Copy link

zacksiri commented Mar 23, 2022

Kibana version: 7.17

Elasticsearch version: 7.17

Server OS version: Elastic CLoud

Browser version: Chrome 99

Browser OS version: MacOS 11.5.2

Original install method (e.g. download page, yum, from source, etc.):

Describe the bug:

CSV exported values do not match what is shown in Kibana

Steps to reproduce:

  1. Index value with text
  2. Go to discover add column
  3. Export as CSV

Expected behavior:

The data should match, in the screenshot below, you can see what is being displayed in Kibana and on the right hand side it's the value in the CSV report generated from kibana. YOu'll see the last 3 digits are 000 and the 4th digit is -1. Something is not right.

Screenshots (if relevant):

Screen Shot 2565-03-23 at 17 00 31

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

@zacksiri zacksiri added the bug Fixes for quality problems that affect the customer experience label Mar 23, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label Mar 23, 2022
@jsanz jsanz added (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Team:Reporting Services labels Mar 24, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Mar 24, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

@tsullivan
Copy link
Member

This looks to be a bug where reporting handles the numeric value by parsing it to a numeric type. It's my understanding that Discover is correctly showing the raw value, but Reporting is converting the value to a numeric type. Reporting's behavior is incorrect because JavaScript isn't able to handle number this high:
image

@tsullivan
Copy link
Member

related: #40183

@tsullivan
Copy link
Member

This issue is specific to when discover:searchFieldsFromSource is ON in Advanced Settings, and only affects CSV export.

@zacksiri
Copy link
Author

@tsullivan thank you for looking into this. You pretty much nailed it and found the root cause of the issue.

@tsullivan
Copy link
Member

Closing as a known issue with discover:searchFieldsFromSource. This setting is labeled as "soon to be deprecated" in the Advanced Settings UI, so I feel OK with leaving this unfixed.

@sophiec20 sophiec20 added the Feature:Reporting:CSV Reporting issues pertaining to CSV file export label Aug 21, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Feature:Reporting:CSV Reporting issues pertaining to CSV file export needs-team Issues missing a team label
Projects
None yet
Development

No branches or pull requests

5 participants