Update arrow example for columnar data

[nitbharambe]

Changes proposed in this PR include:

• Added columnar data example (WIP based on decisions)
• Schema creation

Could you please pay extra attention to the points below when reviewing the PR:

• Table creation is changed to record batch

Decisions

• Keep or remove row based examples?
  • Decided to only keep columnar
• Table creation should be individually or via the schema? Check #TODO Decisions: Create from schema
• Asymmetric attributes should be fixed list array or individual phases or both? Check # TODO Decisions: Asymmetric attributes should be fixed list array or individual phases or both?
• Should we leave update data creation upto users again or provide an example for that as well?

[mgovers]

Should we leave update data creation up to users again or provide an example for that as well?

since this is only an example notebook, not a full feature, i don't think we need to add that. the only difference would be DatasetType.update instead of DatasetType.input

sidenote: i see you add a lot of new cells. is there a need for that? or is it because you haven't removed the old ones yet?

[nitbharambe]

Should we leave update data creation up to users again or provide an example for that as well?

since this is only an example notebook, not a full feature, i don't think we need to add that. the only difference would be DatasetType.update instead of DatasetType.input

sidenote: i see you add a lot of new cells. is there a need for that? or is it because you haven't removed the old ones yet?

Cells regarding decisions will be removed. The final example will be similar size as original.

[mgovers]

CI is failing on code quality

[mgovers]

Suggested change

	"-------asym load scehma-------\n",
	"-------asym load schema-------\n",

[mgovers]

how did this end up in production? please do a follow-up PR to fix this. also double-check that there are no other typos like this remaining

[mgovers]

most of it looks good

[figueroa1395]

Additional nitpick: Although the section for batch data was not updated, I would still add a sentence reminding that it should be provided in columnar format to avoid zero copy (right?) and that it can also be validated. Just to be more self contained, but it is fine as is if you don't deem it necessary.

[nitbharambe]

Additional nitpick: Although the section for batch data was not updated, I would still add a sentence reminding that it should be provided in columnar format to avoid zero copy (right?) and that it can also be validated. Just to be more self contained, but it is fine as is if you don't deem it necessary.

A lot more details can be mentioned about batch data, hence I chose not to mention any of them as it might appear incomplete :D
This point about columnar can indeed be inferred by the user.

In batch case, there would be multiple things to think about:
Different data sources, different batches with multiple scenarios etc. An advanced user would definitely needs to dive deeper there.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud