ZEPPELIN-87: Data order altered in bar chart

[eraffenne]

Fix data order for x axis.

[corneadoug]

Hi,
After trying this branch, my understanding is that the data is now ordered accordingly to the query, is that right?

[eraffenne]

Yes, the data is ordered accordingly to the query.

[corneadoug]

Hi,
I'm not really for merging this PR for multiple reasons:

• Auto ordering can sometimes be helpful at the moment (even if being able to order we want is the goal)
• There is no replacement for ordering outside of the query order
• We are working as part of the Spring Cleaning PR and GSOC into replacing the pivot and ultimately integrating ordering inside of it. (Pivot refactoring coming soon at least), so it would add more cleaning/possible conflicts for us

If however others were inclined to merge:

• Need to remove the commented console.log

This could be eventually merged, and it would be squashed in 3-4weeks maybe. The decision is more about, if people are okay with losing the auto ordering during that time.

[galleon]

Hi,

You mentioned changes in the pivot through GSOC, is there any PR presenting that work? My interest is looking into new visualization (maps especially) so there is obviously a link ;-)

[corneadoug]

@galleon It's early stage for GSOC so no direct PR to Zeppelin repository yet.
In a couple of weeks there should be somewhere I could point you to.

You could also check the angular interpreter which allow you to include any type of view, the documentation was not made yet, but it was merged and you can find examples in the PR itself: #27

Otherwise #56 is changing the code structure and optimizing the code for Zeppelin-web hopefully it will be done soon

[galleon]

@corneadoug I have noticed #56 and I will wait for it to be pushed before contributing.
#27 is impressive and I played a bit with the concept today. Would that allow me to create maps based on D3?

[lucarosellini]

@corneadoug now that #56 has finally been merged we're still experiencing the data order issue fixed by this PR. Is there a chance this will be merged into master?

[corneadoug]

@lucarosellini#56 scope was shortened because of all the changes it was bringing to the project.
So in the end, there was no clear separation of paragraph.js or modification of the pivot, which means the issue still exist.

So far, my feeling was that it was just moving the ordering problem to other cases. (post pivot)
I can run a few test on this PR again, to double check.