+1 for Apache Atlas 2.1.0 RC3 release

Validated the following:
1. Verified the source SHA512 and MD5 checksum
2. Verified the build with -Pdist,embedded-hbase-solr
3. Started Atlas server successfully
4. Verified quick_start.py, all entities and tag get created successfully
5. Created entities, applied tags from UI
6. Checked Basic and advanced search

Regards,
Jayendra.

On Mon, Jul 13, 2020 at 12:17 PM Sarath Subramanian <[email protected]>
wrote:

> +1 for Apache Atlas 2.1 rc3
>
> Validated the following:
> - Validated MD5 checksum
> - Validated sha512 hash
> - Verified PGP signature
> - No binaries in extracted source
> - Built successfully using embedded-hbase and solr profile
> - Ran quick start and tested basic sanity - saved search, basic/advanced
> search, Glossary, tag propagation, Admin purge, system attribute search
>
>
>
> On Thu, Jul 9, 2020 at 9:59 PM Madhan Neethiraj <[email protected]> wrote:
>
> > Atlas team,
> >
> > Apache Atlas 2.1.0 rc3, with following fixes since rc2, is now available
> > for vote within dev community.
> >   ATLAS-3877: Purged entity audit throws 404 Entity not found error
> >   ATLAS-3882: Classic UI: Loader not disappearing while assigning
> category
> > to term
> >
> > Links to the release artifacts are given below. Please review and vote.
> >
> > The vote will be open for at least 72 hours or until necessary votes are
> > reached.
> >   [ ] +1 Approve
> >   [ ] +0 No opinion
> >   [ ] -1 Disapprove (and reason why)
> >
> > Thanks,
> > Madhan
> >
> >
> > List of all issues addressed in this release:
> > https://issues.apache.org/jira/issues/?jql=project=ATLAS AND
> > status=Resolved AND fixVersion=2.1.0 ORDER BY key DESC
> >
> > Git tag for the release:
> > https://github.com/apache/atlas/tree/release-2.1.0-rc3
> > Sources for the release:
> >
> https://dist.apache.org/repos/dist/dev/atlas/2.1.0-rc3/apache-atlas-2.1.0-sources.tar.gz
> >
> > Source release verification:
> >   PGP Signature:
> >
> https://dist.apache.org/repos/dist/dev/atlas/2.1.0-rc3/apache-atlas-2.1.0-sources.tar.gz.asc
> >   SHA512 Hash:
> >
> https://dist.apache.org/repos/dist/dev/atlas/2.1.0-rc3/apache-atlas-2.1.0-sources.tar.gz.sha512
> >   MD5 Hash:
> >
> https://dist.apache.org/repos/dist/dev/atlas/2.1.0-rc3/apache-atlas-2.1.0-sources.tar.gz.md5
> >
> > Keys to verify the signature of the release artifacts are available at:
> > https://dist.apache.org/repos/dist/release/atlas/KEYS
> >
> > New features/enhancements:
> >   - Quick Search: provides a simpler search experience with type-ahead
> > suggestions
> >   - Business Metadata: enables augmenting entity-types with additional
> > attributes, search entities using these attributes
> >   - Labels: ability to add/remove labels on entities, and search entities
> > using labels
> >   - Custom Attributes: ability to add entity instance specific custom
> > attributes i.e. attributes not defined in entity-def or business metadata
> >   - Entity Purge: added REST APIs to purge deleted entities
> >
> > Enhancements:
> >   - Search: ability to find entities by more than one classification
> >   - Performance: improvements in lineage retrieval and
> > classification-propagation
> >   - Notification: ability to process notifications from multiple Kafka
> > topics
> >   - Hive Hook: tracks process-executions via hive_process_execution
> > entities
> >   - Hive Hook: captures DDL operations via hive_db_ddl and hive_table_ddl
> > entities
> >   - Notification: introduced shell entities to record references to
> > non-existing entities in notifications
> >   - Spark: added model to capture Spark entities, processes and
> > relationships
> >   - AWS S3: introduced updated model to capture AWS S3 entities and
> > relationships
> >   - ADLS-Gen2: introduced model to capture Azure Data Lake Storage Gen2
> > entities and relationships
> >   - Dependencies: JanusGraph 0.5.1, Tinkerpop 3.4.6, Spring Framework
> > 4.3.20
> >   - Authorization: updated to cover new features, like: business
> metadata,
> > labels, purge
> >   - UI: multiple UI improvements, including a beta UI
> >
> >
> >
>

Reply via email to