Infer Schema functionality breaks some examples

[matt-hooper]

It appears that the infer schema functionality changed between 0.2.9 and 0.2.11. This has broken some json based examples.

For example, the cryptocurrency example does not work using 0.2.10 (and above) of perspective.
The example reads from a json feed and auto-generates the table schema.

The generated schema is different between the two versions (even though the data from the feed is identical):

Version 0.2.9	Version 0.2.10
client_oid: "string"	-
order_id: "string"	order_id: "string"
order_type: "string"	-
price: "float"	price: "float"
product_id: "string"	product_id: "string"
-	remaining_size: "float"
sequence: "float"	sequence: "float"
side: "string"	side: "string"
size: "float"	-
time: "datetime"	time: "datetime"
type: "string"	type: "string"

The renaming of the size field to remaining_size breaks the example:

I have also seen a similar issue with a different json based data source.
See attached example forecast_min.zip
forecast_min.zip

This example reads data from a json file.
When using 0.2.9 of perspective, the types of the data are correctly inferred:

When 0.2.11 is used, the types are all read as string values. None of the number types are inferred:

Is this new functionality intended?
Is it possible to force perspective to work in the old way and auto infer the number values (without manually passing a pre-defined schema)?

[sc1f]

Definitely a bug inside the type parser—currently working on a fix. Thanks for the report!

[sc1f]

@matt-hooper is the crypto example you mention the one on bl.ocks.org? I have the issue fixed for your forecast data, but I want to see if it fixes the issue on the crypto example as well. Thanks!

[matt-hooper]

@sc1f, yes that is correct. I downloaded the example locally and switched the cdn reference for perspective to a local one, that is when I spotted the issue.

[sc1f]

@matt-hooper the issue looks like it's been resolved for both examples. If you pull the optimize-data-accessor branch, would you let me know if it's been fixed on your end? Thanks!

[matt-hooper]

@sc1f - I have pulled the optimize-data-accessor branch and tested it locally and both issues have been resolved. Thanks for the quick response.

[texodus]

Thanks for the report, this is fixed in 0.2.12