If you want to specify a no_proxy variable in your dockerfile or docker-compose.yml, then this little fix respects the variable in get-requests. Otherwise the proxies could break your docker namespace lookup.

* Handle get schema 404 in pulsar sql(table meta and get splits)

* Fix unit test.

* add defaultSchema()

* use Schema.BYTES.getSchemaInfo()

* add unit test

* rebase and fix unit tests

* Fix swagger of FunctionBase display problem
Signed-off-by: Nxiaolong.ran <ranxiaolong716@gmail.com>

* fix comments
Signed-off-by: Nxiaolong.ran <ranxiaolong716@gmail.com>

Fixes #4914

### Motivation
   1.Go to 'http://pulsar.apache.org/docs/en/admin-api-overview'
   2.Scroll down to 'Java admin client' and click ClientConfiguration link
   3.404 not found error is displayed "The requested URL /api/admin/org/apache/pulsar/client/admin/ClientConfiguration was not found on this server."
   4.the examples can't work.

### Modifications
1.The link to ClientConfiguration  changed to PulsarAdminBuilder.
2.The example changed to 
```
String url = "http://localhost:8080";
// Pass auth-plugin class fully-qualified name if Pulsar-security enabled
String authPluginClassName = "com.org.MyAuthPluginClass";
// Pass auth-param if auth-plugin class requires it
String authParams = "param1=value1";
boolean useTls = false;
boolean tlsAllowInsecureConnection = false;
String tlsTrustCertsFilePath = null;
PulsarAdmin admin = PulsarAdmin.builder()
.authentication(authPluginClassName,authParams)
.serviceHttpUrl(url)
.tlsTrustCertsFilePath(tlsTrustCertsFilePath)
.allowTlsInsecureConnection(tlsAllowInsecureConnection)
.build();
```

*Motivation*

Currently, all transaction buffer code in the transaction module. A transaction buffer inherits `PersistentTopic`, it depends on the pulsar-broker module. When we need to create a transaction buffer at the pulsar-broker, the pulsar-broker depends on the transaction module. So it will cause cyclic reference.

*Modifications*

- move the code under transaction buffer module to the broker module

Fixes #4913 

### Motivation

The original document may mislead users into thinking that there is no any ready-made docker image and building one from scratch.

Fixes #4785

### Motivation

1. Stop return partition name in table list, just return the partitioned topic name in table list. This will avoid huge tables while user create large number of partition.
2. Make partition as internal column, provide users with the ability to get which partition data in and filtration based on partition. For example: 
```
SELECT * FROM "my-table" WHERE "__partition__" = 0;
SELECT * FROM "my-table" WHERE "__partition__" in (2,3);
SELECT * FROM "my-table" WHERE "__partition__" < 1;
```
### Modifications

1. Add "__partition__" internal column.
2. Add domain handle for "__partition__".

### Verifying this change

Added new unit test to verify this change

### Does this pull request potentially affect one of the following parts:

*If `yes` was chosen, please highlight the changes*

  - Dependencies (does it add or upgrade a dependency): (no)
  - The public API: (yes)
  - The schema: (no)
  - The default values of configurations: (no)
  - The wire protocol: ( no)
  - The rest endpoints: (no)
  - The admin cli options: (no)
  - Anything that affects deployment: (no)

### Documentation

  - Does this pull request introduce a new feature? (yes)

Merge Request for #4809: provide a convenient method for C++ client producer batch container (#4885)

provide a convenient method for C++ client producer batch container https://github.com/apache/pulsar/issues/4809

Formally the container element must be used like the following way:
`MessageContainerList::iterator iter = messagesContainerListPtr->begin();`
`iter->sendCallback_(r, iter->message_);`
There are totally 3 reference operation steps inside:

1. Reference an exact element of MessageContainer explicitly from outside by iteration operator;
2. Reference the `sendCallback_` function pointer of said MessageContainer element explicitly from outside;
3. Reference the `message_` member of said MessageContainer element explicitly from outside;

Besides,  there is only one incoming variable say `Result r` is given from outside; 

In an ideal design, a user of `MessageContainer` should not have to know exactly the existence of `MessageContainer::sendCallback_` or `MessageContainer::message_`, what they exactly are, either how to use them.  Organize those stuff in a right way, should be the responsibility of struct `MessageContainer` itself.

So a reasonable convenient invoking method should be like:
`MessageContainerList::iterator iter = messagesContainerListPtr->begin();`
`iter->callBack(r);`

And said `MessageContainer::callBack` function shall be implemented like below:
`void callBack(const pulsar::Result& r) { sendCallback_(r, message_); }`

Obviously, said convenient method is also an efficient one.

Moreover, use a more efficient iteration method while going through the MessageContainerList; 
From some benchmark test result in my local environment, such "for iteration based a fixed-length", will be 5 times faster than the STL::iterator operator way. 

Refer to the change on BatchMessageContainer.cc, please.

---

*Motivation*

There is a error when execute cmake on pulsar-client-cpp

CMake Error at CMakeLists.txt:151 (MESSAGE):
  Could not find Boost Python library

Structure of Schema Chapter: https://github.com/apache/pulsar/issues/4789

* Add support pulsar-kafka-adapter for kafka-0.8 api

clean up pulsar-kafka adapter

add tests

add low level consumer

add simple consumer

corrected pulsar-client-kafka_0_8

fix the module name

add batch and partitioned-topic support

fix headers

add getOffset api support

added pulsarOffset request/response

 clean up

* add pulsar-kafka integration test

* use earliestTime offset

* add default serializer/de

* Fix pulsar admin functions description information
Signed-off-by: Nxiaolong.ran <ranxiaolong716@gmail.com>

* fix comments
Signed-off-by: Nxiaolong.ran <ranxiaolong716@gmail.com>

Motivation
In PR #4764, we allow to create partitioned topic with 1 partition, But in Pulsar Client, user still not able to do it.
This fix try to make sure user could create consumer/producer for 1 partitioned topic .

Modifications
- old and new added unit test passed.

---

*Motivation*

Add default handler to handle transaction related commands.

Fixes #4791

**Motivation**

Currently the Pulsar Kafka wrapper is using Kafka 0.10.x version. However, there are users who use legacy-kafka version in their system and willing to move to pulsar. This PR provides pulsar-kafka adapter for kafka-api-version 0.9.X. So, this adapter can help users in their migration process from kafka-0.9 to pulsar.

### Motivation

Currently, when running Pulsar Functions, Sources, and Sinks in Kubernetes. The resources requests and resource limits are set to the same values.  While this is ok and everything will run as it should, actual resource utilization in the cluster might be low.   To increase actual resource utilization, we need to be able to overcommit a certain amount in our clusters

### Modifications

The checksyle plugin was added to the pulsar sql module to enforce the defined style. All violations were fixed:

- Ordering of imports.
- Formatting of the code.
- Absent Javadoc comments.
- Other small issues.

 MacOS clang/llvm compiler imcompatible code in Unit test case BasicEndToEndTest.cc #4871

### Motivation
Fix concurrent access of `uninitializedCursors` in `ManagedLedgerImpl.asyncOpenCursor`.

### Modifications
* Adds test to expose concurrent access of `uninitializedCursors` in `ManagedLedgerImpl.asyncOpenCursor`.
* Fixes concurrent access of `uninitializedCursors` in `ManagedLedgerImpl.asyncOpenCursor`.

**Motivation**

Fixes #4698 and #4699 

**List of changes**

1. Two new folders under pulsar/deployment/kubernetes/generic : 
- original : contains the original scripts (pre Kubernetes 1.9)
- k8s-1-9-and-above : contains the new scripts with APIs ipdated (Kubernetes 1.9 and above)

2. bookie.yaml :
- Migrate DaemonSet api version from extensions/v1beta1 to apps/v1
- Declare the bookie service before the DaemonSet object for bookies

3. broker.yaml
- Migrate Deployment api version from apps/v1beta1 to apps/v1
- Declare the bookie service before the Deployment object for brokers

4. monitoring.yaml :
- Migrate all Deployment api version from apps/v1beta1 to apps/v1
- Declare each service before the Deployment object the service is bound to

5. zookeeper.yaml :
- Migrate StatefulSet api version from apps/v1beta1 to apps/v1
- Declare the service before the StatefulSet object for zookeeper

6. proxy.yaml
- Migrate Deployment api version from apps/v1beta1 to apps/v1
- Declare the bookie service before the Deployment object for proxy.

* Add *Understand Schema* Section

* Update

* Update

* Update

* update

* Update

* Update

* Update

* Update

* Update

* update

Merge Request for #4808: TYPO in C++ client producer method for processing failure case, and add corresponding unit test case. (#4873)

Definitely, this is a typo. This method is dealing with the Failed Message with the GIVEN result, but not a CERTAIN result.

Contribution Checklist
#4808 : TYPO in C++ client producer method for processing failure case
Add c++ client producer failure message unit test case.

UT passed:

BatchMessageTest

*Motivation*

Add new commands for the transaction.

*Modifications*

- Add new property for `CommandSend`
- Add new command `CommandEndTxnOnPartition`

### Motivation
Incorrect value is being used in Pulsar Helm template `autorecovery-deployment.yaml`

### Modifications
Proper variable name set.

### Verifying this change
Fixed variable name is already set in `values.yaml` and `values-mini.yaml`.
This change is a trivial rework / code cleanup without any test coverage.

### Documentation
None needed.

* improve doc for kerberos

* add more info

* also update 2.4.0 doc

* updated following comments

* change following comments

Fixes #4852

Bug:

After create an empty ledger by sub/unsub and trim ledgers, the first position in managedLedger is ahead of the last when create a consumer without reopen the managed ledger.

Reason：

Last position will be update when opening managedLedger.
Because when creating an empty Ledger without reopening managedLedger, the last position is not be updated. Since the ledger pointed of the last position has been deleted, the first position point to the new ledger.

Fix:

The first position should fall back to last position.

*Modifications*

Add primary operation of transaction. Keep all actions persistently.

Describe the modifications you've done.

- add commit operation
- add abort operation
- add openreader operation

### Motivation

jdbc sink treat all record as INSERT before #4358 , now it requires an indispensable action property which seems to be a break change, and we can deal records without any action property as INSERT.

### Modifications

treat action not set as INSERT action like before.

Fixes #4554 

### Motivation
Add a new deploy tutorial for new Pulsar Functions structure.

### Modifications
Based on the original functions-deploying file, re-adjust the structure and language of functions-deploy.

Structure of Schema Chapter: https://github.com/apache/pulsar/issues/4789

* add thread/process modes

* update the differences between thread and process modes

* update

* update

* Update examples, thread/process modes

* remove process and thread modes

* update

* Refine functions overview and structure

* keep old files and structure, add new ones

* Update

* add a note at the beginning

* create new files for the new structure

* remove two examples

* will create new PR for each of those files

* Update overview

* remove thread/process modes differences

the 0 size limit can't means "infinite" size quota

### Motivation
Continue the issues of #4782

### Verifying this change
Add the tests for it

* [Transaction][buffer] Add data ledger position in txn commit marker
---

*Motivation*

Add the data ledger position into the commit marker of the transaction log.

*Modifications*

Create a new TxnCommitMarker in the proto.