Open table in Voyager option producing incorrect data
See original GitHub issueThis issue concerns the Open Table in Voyager
option.
Here is the code to reproduce this issue.
Currently, with the code from above, I get this result when I right click the pandas dataframe and click the Open Table in Voyager
option.
The data for the related views is not correct, and should look more like this, (just open cars.json
with Voyager)
As you can see, the charts are different in that the data is inconsistent between the two, which should be the same! For instance, the Origin vs Number of Records barchart displayed from the pandas dataframe route is different than the one from opening a json file in Voyager
Issue Analytics
- State:
- Created 5 years ago
- Comments:6
Top Results From Across the Web
Overview of Voyager cataloging client session defaults and ...
Answer. To configure Session Defaults and Preferences in the Voyager Cataloging Client, on the menu bar select Options, then Preferences.
Read more >Voyager - Specific Columns to be displayed on browse
I have changed the model query $query=$model::select('id','owner_name'); which gives me proper single column data on view but still all the ...
Read more >L Voyager Messages
Message ID Message Text Message Type
IDMV000I Voyager reconciliation agent starting Informational
IDFRVI069 Voyager found security subsystem Informational
IDFRVI070 Voyager subpool initialization Ok Informational
Read more >Troubleshooting Misconfigured Fields - Slate Knowledge Base
When building new fields in Slate, users should reference the Fields and Prompts documentation to ensure that the correct settings are...
Read more >Behind Voyager's Fall: Crypto Broker Acted Like a Bank, Went ...
Voyager Digital CEO Steve Ehrlich giving a thumbs up at Bitcoin Miami in April ... Either way, Three Arrows was down bad across...
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
Good catch!
On Thu, Jul 5, 2018 at 3:35 PM Shaheen Sharifian notifications@github.com wrote:
– Brian E. Granger Associate Professor of Physics and Data Science Cal Poly State University, San Luis Obispo @ellisonbg on Twitter and GitHub bgranger@calpoly.edu and ellisonbg@gmail.com
^^^ I think this is a general design question that Jupyter needs to answer properly.
I guess a big aspect of this is how you communicate the data from Python/R/whatever objects to the frontend in javascript and had thought arrow might fit the bill there.
IMHO It would be great if the
Open in Voyager
context menu could be integrated with the variable inspector. They’re already doing something similar by providing a phosphor datagrid view for numpy arrays. Although it’s not yet an officially supported extension I think it would make sense for it to be in future - it’s one of the highest request items from my users.