Skip to content

Commit

Permalink
Merge pull request #5772 from caskdata/docs/r3.4.1_release_notes
Browse files Browse the repository at this point in the history
CDAP 3.4.1 Release Notes
  • Loading branch information
John Jackson committed May 12, 2016
2 parents b5916f4 + 8fcb68b commit 401c9f3
Showing 1 changed file with 121 additions and 0 deletions.
121 changes: 121 additions & 0 deletions cdap-docs/reference-manual/source/release-notes.rst
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,125 @@ Cask Data Application Platform Release Notes
:backlinks: none
:depth: 2

`Release 3.4.1 <http://docs.cask.co/cdap/3.4.1/index.html>`__
=============================================================

Bug Fixes
---------
- `CDAP-4388 <https://issues.cask.co/browse/CDAP-4388>`__ - Fixed a race
condition bug in ResourceCoordinator that prevented performing partition
assignment in the correct order. It affects the metrics processor and
stream coordinator.

- `CDAP-5855 <https://issues.cask.co/browse/CDAP-5855>`__ - Avoid the
cancellation of delegation tokens upon completion of Explore-launched
MapReduce and Spark jobs, as these delegation tokens are shared by CDAP
system services.

- `CDAP-5868 <https://issues.cask.co/browse/CDAP-5868>`__ - Removed
'SNAPSHOT' from the artifact version of apps created by default by the CDAP UI.
This fixes deploying Cask Tracker and Navigator apps, enabling Cask Tracker
from the CDAP UI.

- `CDAP-5884 <https://issues.cask.co/browse/CDAP-5884>`__ - Fixed a bug
that caused SDK builds to fail when using 3.3.x versions of maven.

- `CDAP-5887 <https://issues.cask.co/browse/CDAP-5887>`__ - Fixed the
Hydrator upgrade tool to correctly write out pipeline configs that
failed to upgrade.

- `CDAP-5889 <https://issues.cask.co/browse/CDAP-5889>`__ - The CDAP
Standalone now deploys and starts the Cask Tracker app in the default
namespace if the Tracker artifact is present.

- `CDAP-5898 <https://issues.cask.co/browse/CDAP-5898>`__ - Shutdown
external processes started by CDAP (Zookeeper and Kafka) when there is
an error during either startup or shutdown of CDAP.

- `CDAP-5907 <https://issues.cask.co/browse/CDAP-5907>`__ - Fixed an
issue where parsing of an AVRO schema was failing when it included
optional fields such as 'doc' or 'default'.

- `CDAP-5947 <https://issues.cask.co/browse/CDAP-5947>`__ - Fixed a bug
in the BatchReadableRDD so that it won't skip records when used by
DataFrame.

Known Issues
------------
- After upgrading CDAP from a pre-3.0 version, any unprocessed metrics data in Kafka will
be lost and *WARN* log messages will be logged that tell about the inability to process
old data in the old format.

- `CDAP-797 <https://issues.cask.co/browse/CDAP-797>`__ -
When running secure Hadoop clusters, debug logs from MapReduce programs are not
available.

- `CDAP-1007 <https://issues.cask.co/browse/CDAP-1007>`__ -
If the Hive Metastore is restarted while the CDAP Explore Service is running, the
Explore Service remains alive, but becomes unusable. To correct, restart the CDAP Master
|---| which will restart all services |---| as described under "Starting CDAP Services"
for your particular Hadoop distribution in the :ref:`Installation documentation <installation-index>`.

- `CDAP-1587 <https://issues.cask.co/browse/CDAP-1587>`__ -
CDAP internally creates tables in the "user" space that begin with the word
``"system"``. User datasets with names starting with ``"system"`` can conflict if they
were to match one of those names. To avoid this, do not start any datasets with the word
``"system"``.

- `CDAP-2632 <https://issues.cask.co/browse/CDAP-2632>`__ -
The application in the `cdap-kafka-ingest-guide
<https://github.com/cdap-guides/cdap-kafka-ingest-guide/tree/release/cdap-3.0-compatible>`__
does not run on Ubuntu 14.x as of CDAP 3.0.x.

- `CDAP-2721 <https://issues.cask.co/browse/CDAP-2721>`__ -
Metrics for :ref:`FileSets <datasets-fileset>` can show zero values even if there is
data present, because FileSets do not emit metrics (`CDAP-587
<https://issues.cask.co/browse/CDAP-587>`__).

- `CDAP-2831 <https://issues.cask.co/browse/CDAP-2831>`__ -
A workflow that is scheduled by time will not be run between the failure of the primary
master and the time that the secondary takes over. This scheduled run will not be
triggered at all.

- `CDAP-2920 <https://issues.cask.co/browse/CDAP-2920>`__ - Spark jobs on a
Kerberos-enabled CDAP cluster cannot run longer than the delegation token expiration.

- `CDAP-2945 <https://issues.cask.co/browse/CDAP-2945>`__ -
If the input partition filter for a PartitionedFileSet does not match any partitions,
MapReduce jobs can fail.

- `CDAP-3000 <https://issues.cask.co/browse/CDAP-3000>`__ -
The Workflow token is in an inconsistent state for nodes in a fork while the nodes of
the fork are still running. It becomes consistent after the join.

- `CDAP-3221 <https://issues.cask.co/browse/CDAP-3221>`__ -
When running in CDAP Standalone mode, if a MapReduce job fails repeatedly, then the SDK
hits an out-of-memory exception due to ``perm gen``. The Standalone needs restarting at
this point.

- `CDAP-3262 <https://issues.cask.co/browse/CDAP-3262>`__ -
For Microsoft Windows, the CDAP Standalone scripts can fail when used with a JAVA_HOME
that is defined as a path with spaces in it. A workaround is to use a definition of
JAVA_HOME that does not include spaces, such as ``C:\PROGRA~1\Java\jdk1.7.0_79\bin`` or
``C:\ProgramData\Oracle\Java\javapath``.

- `CDAP-3492 <https://issues.cask.co/browse/CDAP-3492>`__ -
In the CDAP CLI, executing ``select *`` from a dataset with many fields generates an error.

- `CDAP-3641 <https://issues.cask.co/browse/CDAP-3641>`__ -
A RESTful API call to retrieve workflow statistics hangs if units (such as "s" for
seconds) are not provided as part of the query.

- `CDAP-3750 <https://issues.cask.co/browse/CDAP-3750>`__ -
If a table schema contains a field name that is a reserved word in the Hive DDL, ``'enable explore'`` fails.

- `CDAP-5900 <https://issues.cask.co/browse/CDAP-5900>`__ - During the
upgrade to CDAP 3.4.1, publishing to Kafka is halted because the CDAP
Kafka service is not running. As a consequence, any applications that
sync to the CDAP metadata will become out-of-sync as changes to the
metadata made by the upgrade tool will not be published.


`Release 3.4.0 <http://docs.cask.co/cdap/3.4.0/index.html>`__
=============================================================

Expand Down Expand Up @@ -326,6 +445,8 @@ Deprecated and Removed Features
Notifications* to consume only those messages from the audit feed that have the ``type``
field set to ``METADATA_CHANGE``.

.. _known-issues-340:

Known Issues
------------
- After upgrading CDAP from a pre-3.0 version, any unprocessed metrics data in Kafka will
Expand Down

0 comments on commit 401c9f3

Please sign in to comment.