- Add bunch of newly introduced dependencies to the LICENSE file 
- Update dependencies of bookkeeper after upgraded to 4.7.1

* Remove jboss-reflect dependency

*Motivation*

`jboss-reflect` is a LGPL dependency, which is in Category-X and can't be used for apache project.

*Solution*

Removed `jboss-reflect` dependency and replace it with a simple util function to load classes.
Signed-off-by: NSijie Guo <sijie@apache.org>

Signed-off-by: NSijie Guo <sijie@apache.org>

### Motivation

Currently we don't have tools to manage the rack placement configuration for bookies in a Pulsar cluster. 

### Modifications

 * Added `/admin/v2/bookie` REST handler
 * Added `admin.bookie()` in Java admin client
 * Added `pulsar-admin bookies ...` CLI tool 
 * Worked around an issue with bookie hostname and hostname:port that prevented BK client to detect the correct rack.

Fixes #151

In PR #1861, we support  hasMessageAvaliable in reader of cpp client. this is the following work to add wrapper for python.

Change:
- add python and c wrapper
- add test in pulsar_test.py

So that they can be configured to run with TLS.

The certificate authority used to generate the certs is also included
in tests/ with instructions on how to generate new user and server
certs.

These certs will be used for an integration test once #1991 is solved.

* Closing client when Proxyconnection is disconnected

* Addressed massakam's PR comments

* Fixed test failures with authorization disabled

* add admin-api to update function with url

* add cli option for jar-url

Remove pulsar-common dependency from pulsar-io-core module and cleanup pulsar-common dependency references (#2020)

*Motivation*

With pulsar-common shading in pulsar-client, conflicts observed when using pulsar-client with connectors. Because pulsar-client shades its dependencies,
while pulsar-io implementations pull in pulsar-common which depends on non-shaded dependencies.

*Changes*

- Move KeyValue class to pulsar-io-core, since all pulsar-io is using it.
- Remove pulsar-common from all pulsar-io implementation modules
- Cleanup all direct usage of pulsar-common when pulsar-client-original is in the place.

* Begin adding pulsar proxy config docs

* fill out missing config parameters

* add missing license header

* add missing config

This reverts commit 97b56cf0.

Issue 1943: remove serializable from builders and add loadData to load configuration from a config map (#2004)

* Issue 1943: remove serializable from builders and add loadData to load configuration from a config map

*Motivation*

Make pulsar users be able to use java Serialization framework for distributing client settings. This is required for using pulsar in frameworks like Spark.

*Changes*

- Remove serializable from builders
- Add a tool to load client/producer/consumer/reader configuration data from a Map config (which is serializable)

Fixes #1943

* Address review comments:

- add example in javadoc
- change client builder to `loadConf` as well
- change ConfigurationDataUtil to merge config to existing settings
Signed-off-by: NSijie Guo <sijie@apache.org>

* set FAIL_ON_UNKNOWN_PROPERTIES to true
add a test case to make sure exceptions thrown when loading config with unknown properties

* add new doc and add new doc to sidebar index

* add section on client instantiation

* begin adding consumer and reader section

* begin adding consumer options table

* add section on building messages

* add more example code for producers and consumers

* finish draft of go client docs

* update reader definition for popovers

* fix typo in reader definition

* add missing license header

* Updated to go docs

* Fix: set visibility,exclude-libs options to CMAKE_CXX_FLAGS

* Add GCC visibility push(default) for unit test

* Fix undefined reference to auth plugin methods

* Build _pulsar.so without exclude-libs

Previously this log would spam the stdout if there were no messages
coming in. The message wasn't even factually correct, as the timeout
had changed.

I've downgraded the log warn to debug can corrected the factual error.

* Improve pulsar-client shading

*Motivation*

- we should not shade `org.apache.pulsar.common` classes, since they will be used by pulsar api
- Change the shading rules for pulsar-client-admin to make sure they have same shading rules as client, so they can be used together.

*Changes*

- Exclude `org.apache.pulsar.common` from pulsar-client shading rule
- Change shade class prefix for `pulsar-client-admin`

* Use pulsar-client-original in s3-offload integration

* Enable CRC32-C by default in BK client

* Added upgrade notes

* Add key/value operations in StateContext

- add `put` operation to allow state to mutate key/value state
- add `get` operation to allow fetching key/value state
Signed-off-by: NSijie Guo <sijie@apache.org>

* clarification around compacted vs non-compacted consumers

* clarify that no-key msgs are ignored

* theoretical clarifications

* clarify language around listening/changes

*Motivation*

Fixes #1967.

in 2.0 there is an optimization change on grouping acknowledgements.
The [optimization change](https://github.com/apache/incubator-pulsar/commit/19dd2c502725e3b45e56541576508626c4213091#diff-debb36270f152d2533b03902f214fa9aR674)
avoided delivering messages that are already "delivered". However in non-persistent topic, pulsar doesn't store entries to bookkeeper, so no ledger id and entry id
are assigned for those messages. Pulsar uses 0 for both ledger id and entry. So the optimization change treats messages as already "delivered". so pulsar client
doesn't dispatch those messages even it already received them from broker.

*Changes*

- Make AcknowledgementsGroupingTracker an interface
- Introduce a no-op implementation for non-persistent topics
Signed-off-by: NSijie Guo <sijie@apache.org>

* add getlastmessageid and hasMessageAvailable in consmer and reader

* change following comments

* rebase master, change followinw @ivan's comments

### Motivation

Fixes #1049 . The actual fix was included in RocksDB-5.13.3 https://github.com/facebook/rocksdb/issues/2717 and it's now available in Maven central.

The commit that fixed the assertion for empty SSTs was at https://github.com/facebook/rocksdb/commit/8d7396418c11063481ab5b332188509ec0301a7f

* wip

* Removed internal shading

* wip

* Fixed handling of IllegalArgumentException in ZK client wrapper

* wip

* Extend SerDe<T> with Schema<T> and implement PulsarSink

* Add Typed Consumers to functions

* Munge functions and schemas together

* Remove consumer/producer changes

* formatting

* Review changes

* Remove context cache and add setConsumer to context

* Addressed Jerry's comments

* Use pulsar-client-original and fix the tests

This change is enabling bookkeeper table service component in pulsar standalone. So people can try out stateful functions in pulsar.
Signed-off-by: NSijie Guo <sijie@apache.org>

Updates occurrences `establised` to `established`

* Fix: avoid closing RuntimeFactory when any function stops

* close runtimeFactory for process-runtime

* Add function-package-url support in function cli

add url support to function cli

* file-url comment

* add server-side validation for source/sink class and arg-type

remove cmd-line args

* Fixed python extension build

* Added comment

* Fix topic name in getting started documentation

It was "my-topic", when it should have been
persistent://public/default/my-topic.

* Remove topic changes

*Motivation*

Fixes #1929

*Changes*

Per [comment](https://github.com/apache/incubator-pulsar/issues/1929#issuecomment-395497432),
we don't need to specify `--advertised-address` after 1.22.0

* Added release notes for 2.0.1-incubating release`

* Fixed tag link