You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am suffering from the same problem, after generating the connected components, a component is generated that attaches many nodes that are unconnected. I have tried the options mentioned in the thread (collapse the spark graph using the round trip, make a previous count, use a repartition) but nothing works, I keep receiving as output a component that agglutinates millions of nodes, and whose number is usually 0 but oscillates.
I have no more ideas to resort to, I don't know if anyone has any idea that could help, it would be of great help.
Thank you very much for your help.
The text was updated successfully, but these errors were encountered:
Fwiw, I've noticed this behavior when AQE is enabled. If I disable it directly before calling connected components, it works as expected in my case ...
Same issue. Writing/Reading vertices and edges to disk worked in my case.
Another workaround: replace call to monotonically_increasing_id() by zipWithUniqueId. This means the DataFrame has to be converted to an RDD and back to a DataFrame again. It seems to work as well.
Hello good evening,
I am suffering from the same problem, after generating the connected components, a component is generated that attaches many nodes that are unconnected. I have tried the options mentioned in the thread (collapse the spark graph using the round trip, make a previous count, use a repartition) but nothing works, I keep receiving as output a component that agglutinates millions of nodes, and whose number is usually 0 but oscillates.
I have no more ideas to resort to, I don't know if anyone has any idea that could help, it would be of great help.
Thank you very much for your help.
The text was updated successfully, but these errors were encountered: