Add neo4j-admin-import section and parameter details for Parquet. #1850
Conversation
|
Just to be extra explicit: the feature has been merged so this PR can be reviewed/merged too. |
I am reviewing the PR now, but I see that @meistermeier is on vacation. So, I'll just push my editorial and style changes into the PR. We can always discuss and improve them later when he is back. Having said that, I'll still need someone to review my commit. |
|
Also, I need to see why the test is failing. |
|
@renetapopova I'm covering for @meistermeier. I can work on any updates you deem necessary. |
Ah, cool! As I said, I pushed some editorial updates if you want to take a look, but I think the content looks good for merging. However, the |
renetapopova
force-pushed
the
parquet-import
branch
from
1ab00ee to
2942f72
Compare
Move unsupported parameters by the Parquet importer to their own section.
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
|
Closing this one as duplicate. |
renetapopova
added
duplicate
…1858) The Parquet file support for neo4j admin import will come out in on of the next minor versions as a preview feature. Depending on the feedback we get from customers and users, there will be definitely coming more (also to the docs). This is a quite defensive change to avoid promising too much but also pointing out that this feature exists at all ;) Because the feature itself is not merged yet, I added the DO NOT MERGE label. Please let us get this into a shape where we can just merge it after the feature went into the product, thanks. This supersedes #1850 --------- Co-authored-by: Gerrit Meier <[email protected]> Co-authored-by: Reneta Popova <[email protected]>
4 participants
The Parquet file support for neo4j admin import will come out in on of the next minor versions as a preview feature.
Depending on the feedback we get from customers and users, there will be definitely coming more (also to the docs).
This is a quite defensive change to avoid promising too much but also pointing out that this feature exists at all ;)
Because the feature itself is not merged yet, I added the DO NOT MERGE label.
Please let us get this into a shape where we can just merge it after the feature went into the product, thanks.