search

neo4j / neo4j

Graphs for Everyone
http://neo4j.com
GNU General Public License v3.0
13.29k stars 2.38k forks source link

Remove known property keys from database #10941

Open dennisverspuij opened 6 years ago

dennisverspuij commented 6 years ago

It would be great if one could CALL db.removeProperty([key]) to remove all properties set with given key from any nodes as well as the Neo4j indexes, so that subsequent CALL db.propertyKeys() won't include that key anymore. Or CALL db.removeUnusedPropertyKeys() to just drop all keys that are not in use. This would solve the annoyance as described here.

Would this be possible? Or is there any other way to remove property keys currently that I am not aware of?

Thanks!

Lojjs commented 6 years ago

@dennisverspuij Thanks for your feature request, it sounds like a useful thing. We will review the priority of this and consider it for future development.

Best regards Louise, Neo4j Cypher team

64BitAsura commented 6 years ago

@Lojjs may I know what status of this feature request ? :)

Lojjs commented 6 years ago

@sambathl This is on our long list of feature request but unfortunately it isn't considered of high enough priority to be worked on right now.

vjoks commented 5 years ago

during development phase especially query initial testing is done on the browser. As time goes on, all the unused property keys clutter the cached values in the browser, including the ones with typos. Please provide a way to either repopulate the cache or delete specific ones.

As the project and the team get bigger, it is a nightmare to see these unused/incorrect property keys which no longer are in the DB show up on the browser. HELP improve usability.

cdornfeldnj commented 5 years ago

This would be a welcome "quality of life" improvement for our team, too.

jschmidtWK commented 5 years ago

I strongly support this as well. As the project grows this can induce critical mistakes.

Having auto-completion is useful, but if half the time the provided completion is false or deceptive (like case issues or typos), it can lead to significant delays and troubles.

venkat125 commented 5 years ago

@Lojjs Hai, dev / BA folks, requesting to release this feature ASAP, as it ensures some robustness of the DB feature. Looking forward to have this, Bcoz, as continuing of adding nodes, it seems to be difficult to handle the unused / mis-entered / typo error property key.

Seems everyone is waiting. Hope u consider tis. I'm waiting :) Interested in hearing from you people. Thanks in advance.

Muzosh commented 4 years ago

Hello, any new progress on this request?

chrisvest commented 4 years ago

In 4.0 you can do this off-line with neo4j-admin copy --skip-properties propA,propB,propEtc ...

Muzosh commented 4 years ago

@chrisvest This doesn't seem to be an option for neo4j-admin command image

chrisvest commented 4 years ago

@muzos07 Your version only has neo4j-admin copy in the Enterprise Edition, but we're moving it to Community Edition in, like, 4.0.4 I think.

rmacd commented 3 years ago

I take it neo4j-admin copy didn't make it into 4.0.4 (or version after 4.0.4 for that matter)? ;-)

lifeisbard commented 3 years ago

Please implement neo4j-admin copy in the Community Edition. The unused properties that appear in the Neo4j Browser autocomplete and "Property Keys" section of the "Database" tab are clutter. A tidy virtual workspace supports efficiency. Thank you in advance.

Farxial commented 2 years ago

If the property key deletion is too difficult to implement, why not implement property key rename? Usage scenario:

  1. Remove the deprecated property from all entities
  2. Review property-related constraints
  3. Rename the property key to give it a new life
  4. Enjoy :)
sify21 commented 9 months ago

In version 5 it's neo4j-admin database copy, only available in Enterprise Edition

Dabnis commented 2 weeks ago

Just a FYI: I was tasked with demonstrating neo4j to my CTO (multi-national company), he was quick to pick up on the mess of historic & unused stuff that your browser produces. Does not look good; professional, or stable were his comments. Given the visibily & how long this issue has been outstanding, how it damages your brand. As an engineer myself I can only assume that either: A) you don't know what the cause is, or B) you are not capable of fixing it. As a company we are now implementing tigergraph & memgraph. I'm sure that you have lost many more potential clients for the same reason. Bye

nether-cat commented 2 weeks ago

Just a FYI: I was tasked with demonstrating neo4j to my CTO (multi-national company), he was quick to pick up on the mess of historic & unused stuff that your browser produces. Does not look good; professional, or stable were his comments. Given the visibily & how long this issue has been outstanding, how it damages your brand. As an engineer myself I can only assume that either: A) you don't know what the cause is, or B) you are not capable of fixing it. As a company we are now implementing tigergraph & memgraph. I'm sure that you have lost many more potential clients for the same reason. Bye

That’s true.