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

Feature relatable #1090

Merged
merged 5 commits into from
May 27, 2020
Merged

Feature relatable #1090

merged 5 commits into from
May 27, 2020

Conversation

huboneo
Copy link
Contributor

@huboneo huboneo commented Apr 29, 2020

This PR introduces a new configuration option in browser for truncating max field length before they are passed to rendering layers. The reason for this is that certain queries can produce a single result with a lot of values in a given field, which we had yet to account for.

This PR also adds @relate-by-ui/relatable table to improve rendering performance.

Finally this PR also adds a max limit before Viz is disabled as it cannot handle more than 1000 rendered nodes/relationships

STR

  • see trello card

Screenshot

Screenshot 2020-04-29 at 11 36 52

Screenshot 2020-04-29 at 11 46 03

Screenshot 2020-04-29 at 11 38 46

Screenshot 2020-04-29 at 11 39 07

changelog: Add a more performant result table

@huboneo
Copy link
Contributor Author

huboneo commented May 19, 2020

@oskarhane I have passing tests now apart from 4.1

Copy link
Member

@oskarhane oskarhane left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome, renders all types as we want it to! Nice!

Screenshot 2020-05-26 14 00 28

Just one last thing, I think the recursive lookup for graph elements isn't working properly.
This query on the regular movies db doesn't render anything in the viz view:

MATCH (n:Person)-[r]-()
RETURN 1.0, 1, null, true, false, "hello", "<b>bold</b>", [1, "x"], {x: 1, y: "string", n: n, html: "<b>bold</b>", link: "x http://hej.com x"}, r

huboneo added 5 commits May 27, 2020 13:58
- Introduced new setting "maxFieldItems"
- Now truncating data passed to CypherFrames whenever a field that is too large is detected
- Refactored boltMapping code to increase performance
- Side effect is that we now dedupe nodes, not sure if OK
- fix unit test
- update snapshots, add warning when fields are truncated
- Replaced TableView with RelatableView
- Updated tests
- Removed max field items from settings for now, use :config
- Also disabled Vis when results exceed max safe limit
@huboneo huboneo force-pushed the feature-relatable branch from 17a356c to 8b58fe9 Compare May 27, 2020 12:01
@huboneo
Copy link
Contributor Author

huboneo commented May 27, 2020

@oskarhane great catch, updated!

Copy link
Member

@oskarhane oskarhane left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@huboneo huboneo merged commit 19c95f6 into neo4j:master May 27, 2020
@huboneo huboneo deleted the feature-relatable branch May 27, 2020 14:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants