Describe the bug
A clear and concise description of what the bug is.

KSQLDB fails to start if ssl.keystore.type=pkcs12 instead of ssl.keystore.type=PKCS12

To Reproduce
Steps to reproduce the behavior, include:

1. The version of KSQL.
2. Sample source data.
3. Any SQL statements you ran

Latest version of KSQLDB with Java 11 and FIPS support enabled.

Expected behavior
A

Is your enhancement proposal related to a problem? Please describe.
Syscalls run on fixed-sized privilege elevation stacks. There is a hard limit on how much stack space a system call can use because of this. We don't have good data on how much stack syscalls actually use.

Describe the solution you'd like
I'd like to be able to use CONFIG_STACK_USAGE to be able to generate a report,

Bug Report

Steps to Reproduce:

1. Create a dataframe with a categorical axis.
2. Attempt to load into a PerspectiveWidget or Table.

Expected Result:

A valid widget or Table.

Actual Result:

---------------------------------------------------------------------------
PerspectiveError                          Traceback (most recent call last)
<ipython-i

Hey everyone!

mapd-core-cpu is already available on conda-forge (https://anaconda.org/conda-forge/omniscidb-cpu)

now we should add some instructions on the documentation.

at this moment it is available for linux and osx.

some additional information about the configuration:

1. for now, always install omniscidb-cpu inside a conda environment (also it is a good practice), eg: