Known Issues
It's on our radar.
If you come across something not covered here, please email us at documentation@arcadiadata.com.
ADMIN API: Calls that use API tokens may not work
- Description
- For all token-based administrative API calls, like calls from python-based
scripts, the calls may fail with errors, or return blank results.
- Workaround
-
Perform these steps:
-
Add the following parameter to ArcViz
settings.py
file:
ADMINAPI_REQUIRE_APIKEY = True
- Restart the Arcadia Visualization Server, ArcViz.
- Domain
- System Administration
ARCENGINE: Must Have Directory arcengine-scratch
- Description
-
Arcadia Engine throws an exception when inserting, or when refreshing
analytical views.
Arcadia Engine installs and uses the directory
/tmp/arcengine-scratch
. This directory may be
removed by the user accidentally, or as a result of a reboot.
- Workaround
- Create the directory manually.
- Domain
- Analytical Views, Installation
ARCENGINE: Logging Level Set to 0 by Default
- Description
-
During installation, the Arcadia Engine logging level defaults to level
0. This excludes information about query execution from the logs.
- Workaround
-
Change the Arcadia Analytics Engine Minimum Log
Verbosity
to 1 during installation.
- Domain
- Logging
ARCENGINE: Daemon is Over the Memory Limit
- Description
-
On Cloudera Installs, Arcadia Engine defines the minimum memory limit at
install time through the configuration attribute Memory
Limit
, and sets it to 64 MB by default. An overcommitted
Cloudera node may cause the Arcadia Engine memory allocation to shrink
to this size, which may prove to be insufficient for reasonable
workloads.
- Workaround
-
After installing Arcadia Service, change the configuration attribute
Memory Limit
to the recommended memory size of 8
GB. We recommend this change for any installation where Memory
Limit
is currently at 64 MB.
- Domain
-
Administration, Installation
EMAIL: Emailing Visuals with Non-ASCII Characters in Title or Email Subjects
Fails
- Description
-
Visuals that include non-ASCII characters in their title, or in the
subject of the email cannot be sent over email successfully. Instead,
they do not complete and remain in the “running” state.
- Workaround
- Change the name of the visual and/or the email subject to exclude or replace
non-ASCII characters.
- Domain
- Administration, Visualization, Settings
EMAIL: No Monitoring for Messages Sent to Non-Existing Email Addresses
- Description
- Arcadia does not monitor if emails sent to non-existing emails succeed.
Arcadia does perform a basic validation for correct syntax in email
addresses.
- Workaround
- None
- Domain
- Administration, Visualization, Settings
MIGRATION: Schema Check not Performed
- Description
-
When migrating visual artifacts, there is no checking that the data table
schema of the destination system matches the source.
- Workaround
- Manually check that the table schemas for all visual artifacts on the
destination system matches the source, or that it is a super-set of the
source schemas.
- Domain
- Migration, Utilities
PNG Export and Thumbnails for Custom JS Support
- Description
- PNG Snapshot Export and Thumbnails for custom visuals support only ECMA
Script 5 for JavaScript.
- Workaround
- Ensure that your JS version complies with ECMA Script 5.
- Domain
- Administration, Visualization
PNG Export and Thumbnails on Linux Platforms Have Package Dependencies
- Description
-
In CDH Parcel installations, PNG Export and Thumbnail generation may not
work correctly.
- Workaround
- These features require the presence of third-party
fontconfig
, freetype
,
xorg-x11-font-utils
, and urw-fonts
packages. Use the following command to install the appropriate
dependencies:> sudo yum install fontconfig freetype xorg-x11-font-utils urw-fonts
- Domain
- Administration, Visualization
CONNECTION: User-defined Aggregate Expressions Marked as Non-Aggregates
- Description
-
This occurs on Arcadia, Spark SQL, Hive, Impala, and Oracle
connections:
- In Release 4.1.5.1, when a user defines aggregate expressions on a
field in dataset interface, they may be incorrectly marked as
non-aggregates.
- In Release 4.2.0.0, when a user defines non-aggregate expressions on
a field in dataset interface, they may be incorrectly marked as
aggregates.
- Workaround
- Save the user-defined field in the dataset again.
- Domain
- Connecting, Visualization
CONNECTION: User-Defined Aggregate Expressions Do Not Validate
- Description
- On all connections, when a user enters an aggregate expression in the
Enter /Edit Expression interface, the expression fails
validation. However, the query runs as expected.
- Workaround
- Save without validating the expression.
- Domain
- Connecting, Visualization
CONNECTION: User-Defined Numeric Expressions Do Not Validate
- Description
- On Hive connections, when a user creates a new numeric expression in the
Enter /Edit Expression interface, it fails validation and reports
an error that the column does not exist. However, the query runs as
expected.
- Workaround
- Save without validating the expression.
- Domain
- Connecting, Visualization
CONNECTION: Query Fails if Dataset Column Names Invoked Without Brackets
- Description
- On SQLite connections, when a user defines a dataset column name and uses it
without brackets in the Enter /Edit Expression interface, the
expression validates, but the query fails at run time.
- Workaround
- Ensure that column names in the expressions use brackets, like this:
[field_name]
.
- Domain
- Connecting, Visualization