Smeet Nagda

I was actually thinking about the same, if we could represent it in a kind off pretty json format it would provide better understandability of the input

> Hm the `Select` transform works differently in Python, I think we should actually have different language for this entire section for Python. Could you elaborate please? Is the syntax...

> In general our Python schema transforms are different, we might want an entirely new "Using Schema Transforms" section specific to Python that discusses the GroupBy and Select transforms. >...

Oh okay got it that's what I was wondering whether it was nested fields and wildcards which didn't work in python, I guess we could remove this section for python...

no problem! , should I remove this section from python for now or should we wait for the new feature and just add the examples later ?

alright on it

@TheNeuralBit every example in section 6.6 (maps, grouping aggregations, joins, complex joins uses nested fields, should I keep the whole thing specific to java ?

There was no language tag in each paragraph so the paragraph was shown irrespective of language selected I thought by adding {{< paragraph class="language-java" >}} the paragraph would be only...

I'll look more into paragraph tags and see why it didn't work

@yeandy I've added paragraphs for python saying the support hasn't been developed yet. Could you check whether there are visual changes or not