You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tubemq.apache.org by Goson zhang <go...@apache.org> on 2021/03/24 02:57:18 UTC
[Monthly report] Project progress feedback
Hello everyone:
The community of the project has been a bit quiet recently, not everyone is
asleep, we are dealing with the following content:
1. The content preparation of the rename project:
According to our previous discussion of renaming, our mentor has submitted
a renaming Jira[1] (thanks to mentor JB), we need to organize the relevant
project content before the implementation of the renaming, including the
new project homepage, Logo, other open source components, etc.
Please wait, it is expected that the overall content of the project will be
updated after the name change is completed at the end of March, or early
April if the rename operation delays.
2. Metadata store component transformation:
This part is performing online, refer to the branch TUBEMQ-570. Due to the
license issue of BDB, we need to switch the metadata storage and the
keep-alive mechanism of the system to Zookeeper. Since this part is a
replacement of basic components, there is a transition, which will switch
to zk after the code abstraction is completed. and anyone interested can
pay attention to this branch.
3. Development tubemq-manager node:
This part is also carried out online, refer to the branch TUBEMQ-421. The
requirement of this part is to be an independent management node that spans
multiple TubeMQ clusters to facilitate system operation and maintenance.
As the related changes are relatively large work, we are going to release
the version after the rename of InLong is completed. So, for users of
TubeMQ 0.8.0 version, there is a problem that needs to be paid attention
to, a bug was recently discovered [2], which affects the information query
of webAPI. Before the version is released, please refer to the issue[2] and
fix it self:
1.
https://issues.apache.org/jira/projects/INFRA/issues/INFRA-21558?filter=allopenissues
2.
https://issues.apache.org/jira/projects/TUBEMQ/issues/TUBEMQ-577?filter=doneissues
If you have any questions, feedback is welcome.
Thanks all!
Re: [Monthly report -- 20210630] Project progress feedback
Posted by Goson zhang <go...@apache.org>.
Sorry for keeping everyone waiting
We have reinitialized the project, and we will build Apache InLong into a
one-stop data access platform through the community, helping businesses to
easily build stream-based data application services based on this platform.
Thanks!
Goson zhang <go...@apache.org> 于2021年6月30日周三 上午10:52写道：
> Hi all:
>
> We started to merge relevant code according to the adjustment of the
> project goal
>
> After the first version is merged, we will discuss the planning of the
> roadmap according to the project goals next.
>
> Thanks!
>
>
> ---------- Forwarded message ---------
> 发件人： Goson zhang <go...@apache.org>
> Date: 2021年6月17日周四 上午10:15
> Subject: Re: [Monthly report -- 20210528] Project progress feedback
> To: <de...@inlong.apache.org>
>
>
> Hi all:
> Recently, we are going to make code and document changes in accordance
> with InLong’s adjustment plan, and related PRs merge are temporarily
> frozen, sorry!
>
> We hope that the adjusted project can better help those in need
>
> Thanks!
>
>
> Goson zhang <go...@apache.org> 于2021年5月28日周五 下午4:18写道：
>
>> Sorry, when the translation content is too long, I am not sure whether
>> the translation software can understand what I want to say.
>>
>> In general, the project is gradually attracting people who really pay
>> attention and use it, and the project will be adjusted from next month.
>>
>> Thanks!
>>
>> Goson zhang <go...@apache.org> 于2021年5月28日周五 下午4:12写道：
>>
>>> Hello everyone:
>>>
>>> Summarize the recent situation:
>>> 1. Branch 570: now it has entered the testing phase, after this content
>>> is launched, the readability and scalability of Web APIs and metadata
>>> management will be more better, which is convenient for subsequent feature
>>> expansion; due to the compatibility of previous versions, the old version
>>> of the API and the underlying BDB data storage classes are still retained,
>>> although these old APIs and storage formats are somewhat obsolete;
>>>
>>> 2. Branch 25: pure Go language SDK, compared with the previous stage,
>>> the contributors of this module have already started actual code
>>> contributions. If you are interested in Go language implementation and want
>>> to participate, you can pay attention to its issue.
>>>
>>> 3. The main body of InLong will start to move next month: thanks mentor @Justin,
>>> @JB have prepared the basic environment of the project. Everyone may
>>> pay attention that InLong's code and website content have not been adjusted
>>> according to the name change (maybe the people involved in this project are
>>> asleep), and someone who chooses to contribute to this problem. First of
>>> all, thank contributors @RocMarshal and @leven-space for finding this
>>> problem and Initiated an improvement; considering that the changes are too
>>> large, we will release it when we are ready, and track the content of each
>>> improvement through INLONG-613 and INLONG-614, until all the content is
>>> prepared on the branch, and then merged into the project master.
>>>
>>> 4. A code contribution Tips：when we contribute, we must consider the
>>> issue of originality and respect for originality, when we contribute code,
>>> if we directly quote external code, we need to declare in the LICENSE and
>>> NOTICE of the project, which files are quoted from where, or else it will
>>> form infringement; as we directly quote external codes, the LICENSE and
>>> NOTICE of the ontology project will expand, this result will make people
>>> feel that the project is a hodgepodge. TubeMQ did not consider this issue
>>> at first, now we will reduce the direct quotation of the source code of
>>> external projects, so we should be as original as possible when
>>> contributing code.
>>>
>>> The last, after the metadata management transformation is completed, in
>>> addition to switching the BDB storage module, we will also renovate some
>>> old implementations. If you see some bad implementations, please feel free
>>> to contribute.
>>>
>>> Thanks all!
>>>
>>>
>>> ---------- Forwarded message ---------
>>> 发件人： Goson zhang <go...@apache.org>
>>> Date: 2021年4月30日周五 上午9:46
>>> Subject: [Monthly report -- 20210430] Project progress feedback
>>> To: <de...@inlong.apache.org>
>>>
>>>
>>> Hello everyone:
>>>
>>>
>>> Recent project progress:
>>> 1. Branch 570 has completed the refactoring of the Web APIs: about 80
>>> APIs have been adjusted according to the new plan, next, the application
>>> logic MetaDataManager class of metadata will be adjusted. After adjustments
>>> are finished, the tests will be performed, including unit tests,
>>> integration test, compatibility test, and verification are passed, and
>>> then the document is written, finally merged into the main branch. After
>>> the main line branch is merged, the development branch of the metadata
>>> removal BDB component will be started.
>>>
>>> 2. The SDK of pure Go language has also been assigned(INLONG-25): A man
>>> who is concerned about the project and willing to contribute to our project
>>> has done an analysis and started the code implementation. The charm of the
>>> open source community is that it is as if a seed has been planted, and it
>>> begins to sprout and grow without knowing it.
>>>
>>> 3. The InLong project is slowly gathering resources, and an initial
>>> version will be released as soon as possible: since rename took nearly 4
>>> months from the time the application was filed to the final implementation,
>>> which was far more than expected, so, the resources gathered in the early
>>> stage, need to gradually join in, but don't worry, things are changing.
>>>
>>> By the way, I saw that the latest version of Kafka has removed the
>>> zookeeper, great! TubeMQ has removed zookeeper from the core logic around
>>> 2017. But now to comply with Apache's LICENSE specification, we will also
>>> consider supporting metadata storage components including Zookeeper :).
>>>
>>> That's it, happy May Day, everyone!
>>>
>>> Thanks!
>>>
>>>
>>> ---------- Forwarded message ---------
>>> 发件人： Goson zhang <go...@apache.org>
>>> Date: 2021年3月24日周三 上午10:57
>>> Subject: [Monthly report] Project progress feedback
>>> To: <de...@tubemq.apache.org>
>>>
>>>
>>> Hello everyone:
>>>
>>> The community of the project has been a bit quiet recently, not everyone
>>> is asleep, we are dealing with the following content:
>>>
>>> 1. The content preparation of the rename project:
>>> According to our previous discussion of renaming, our mentor has
>>> submitted a renaming Jira[1] (thanks to mentor JB), we need to organize the
>>> relevant project content before the implementation of the renaming,
>>> including the new project homepage, Logo, other open source components, etc.
>>> Please wait, it is expected that the overall content of the project will
>>> be updated after the name change is completed at the end of March, or early
>>> April if the rename operation delays.
>>>
>>> 2. Metadata store component transformation:
>>> This part is performing online, refer to the branch TUBEMQ-570. Due to
>>> the license issue of BDB, we need to switch the metadata storage and the
>>> keep-alive mechanism of the system to Zookeeper. Since this part is a
>>> replacement of basic components, there is a transition, which will switch
>>> to zk after the code abstraction is completed. and anyone interested can
>>> pay attention to this branch.
>>>
>>> 3. Development tubemq-manager node:
>>> This part is also carried out online, refer to the branch TUBEMQ-421.
>>> The requirement of this part is to be an independent management node that
>>> spans multiple TubeMQ clusters to facilitate system operation and
>>> maintenance.
>>>
>>> As the related changes are relatively large work, we are going to
>>> release the version after the rename of InLong is completed. So, for users
>>> of TubeMQ 0.8.0 version, there is a problem that needs to be paid attention
>>> to, a bug was recently discovered [2], which affects the information query
>>> of webAPI. Before the version is released, please refer to the issue[2] and
>>> fix it self:
>>>
>>> 1.
>>> https://issues.apache.org/jira/projects/INFRA/issues/INFRA-21558?filter=allopenissues
>>> 2.
>>> https://issues.apache.org/jira/projects/TUBEMQ/issues/TUBEMQ-577?filter=doneissues
>>>
>>> If you have any questions, feedback is welcome.
>>>
>>> Thanks all!
>>>
>>>
>>>
[Monthly report -- 20210630] Project progress feedback
Posted by Goson zhang <go...@apache.org>.
Hi all:
We started to merge relevant code according to the adjustment of the
project goal
After the first version is merged, we will discuss the planning of the
roadmap according to the project goals next.
Thanks!
---------- Forwarded message ---------
发件人： Goson zhang <go...@apache.org>
Date: 2021年6月17日周四 上午10:15
Subject: Re: [Monthly report -- 20210528] Project progress feedback
To: <de...@inlong.apache.org>
Hi all:
Recently, we are going to make code and document changes in accordance with
InLong’s adjustment plan, and related PRs merge are temporarily frozen,
sorry!
We hope that the adjusted project can better help those in need
Thanks!
Goson zhang <go...@apache.org> 于2021年5月28日周五 下午4:18写道：
> Sorry, when the translation content is too long, I am not sure whether the
> translation software can understand what I want to say.
>
> In general, the project is gradually attracting people who really pay
> attention and use it, and the project will be adjusted from next month.
>
> Thanks!
>
> Goson zhang <go...@apache.org> 于2021年5月28日周五 下午4:12写道：
>
>> Hello everyone:
>>
>> Summarize the recent situation:
>> 1. Branch 570: now it has entered the testing phase, after this content
>> is launched, the readability and scalability of Web APIs and metadata
>> management will be more better, which is convenient for subsequent feature
>> expansion; due to the compatibility of previous versions, the old version
>> of the API and the underlying BDB data storage classes are still retained,
>> although these old APIs and storage formats are somewhat obsolete;
>>
>> 2. Branch 25: pure Go language SDK, compared with the previous stage, the
>> contributors of this module have already started actual code contributions.
>> If you are interested in Go language implementation and want to
>> participate, you can pay attention to its issue.
>>
>> 3. The main body of InLong will start to move next month: thanks mentor @Justin,
>> @JB have prepared the basic environment of the project. Everyone may pay
>> attention that InLong's code and website content have not been adjusted
>> according to the name change (maybe the people involved in this project are
>> asleep), and someone who chooses to contribute to this problem. First of
>> all, thank contributors @RocMarshal and @leven-space for finding this
>> problem and Initiated an improvement; considering that the changes are too
>> large, we will release it when we are ready, and track the content of each
>> improvement through INLONG-613 and INLONG-614, until all the content is
>> prepared on the branch, and then merged into the project master.
>>
>> 4. A code contribution Tips：when we contribute, we must consider the
>> issue of originality and respect for originality, when we contribute code,
>> if we directly quote external code, we need to declare in the LICENSE and
>> NOTICE of the project, which files are quoted from where, or else it will
>> form infringement; as we directly quote external codes, the LICENSE and
>> NOTICE of the ontology project will expand, this result will make people
>> feel that the project is a hodgepodge. TubeMQ did not consider this issue
>> at first, now we will reduce the direct quotation of the source code of
>> external projects, so we should be as original as possible when
>> contributing code.
>>
>> The last, after the metadata management transformation is completed, in
>> addition to switching the BDB storage module, we will also renovate some
>> old implementations. If you see some bad implementations, please feel free
>> to contribute.
>>
>> Thanks all!
>>
>>
>> ---------- Forwarded message ---------
>> 发件人： Goson zhang <go...@apache.org>
>> Date: 2021年4月30日周五 上午9:46
>> Subject: [Monthly report -- 20210430] Project progress feedback
>> To: <de...@inlong.apache.org>
>>
>>
>> Hello everyone:
>>
>>
>> Recent project progress:
>> 1. Branch 570 has completed the refactoring of the Web APIs: about 80
>> APIs have been adjusted according to the new plan, next, the application
>> logic MetaDataManager class of metadata will be adjusted. After adjustments
>> are finished, the tests will be performed, including unit tests,
>> integration test, compatibility test, and verification are passed, and
>> then the document is written, finally merged into the main branch. After
>> the main line branch is merged, the development branch of the metadata
>> removal BDB component will be started.
>>
>> 2. The SDK of pure Go language has also been assigned(INLONG-25): A man
>> who is concerned about the project and willing to contribute to our project
>> has done an analysis and started the code implementation. The charm of the
>> open source community is that it is as if a seed has been planted, and it
>> begins to sprout and grow without knowing it.
>>
>> 3. The InLong project is slowly gathering resources, and an initial
>> version will be released as soon as possible: since rename took nearly 4
>> months from the time the application was filed to the final implementation,
>> which was far more than expected, so, the resources gathered in the early
>> stage, need to gradually join in, but don't worry, things are changing.
>>
>> By the way, I saw that the latest version of Kafka has removed the
>> zookeeper, great! TubeMQ has removed zookeeper from the core logic around
>> 2017. But now to comply with Apache's LICENSE specification, we will also
>> consider supporting metadata storage components including Zookeeper :).
>>
>> That's it, happy May Day, everyone!
>>
>> Thanks!
>>
>>
>> ---------- Forwarded message ---------
>> 发件人： Goson zhang <go...@apache.org>
>> Date: 2021年3月24日周三 上午10:57
>> Subject: [Monthly report] Project progress feedback
>> To: <de...@tubemq.apache.org>
>>
>>
>> Hello everyone:
>>
>> The community of the project has been a bit quiet recently, not everyone
>> is asleep, we are dealing with the following content:
>>
>> 1. The content preparation of the rename project:
>> According to our previous discussion of renaming, our mentor has
>> submitted a renaming Jira[1] (thanks to mentor JB), we need to organize the
>> relevant project content before the implementation of the renaming,
>> including the new project homepage, Logo, other open source components, etc.
>> Please wait, it is expected that the overall content of the project will
>> be updated after the name change is completed at the end of March, or early
>> April if the rename operation delays.
>>
>> 2. Metadata store component transformation:
>> This part is performing online, refer to the branch TUBEMQ-570. Due to
>> the license issue of BDB, we need to switch the metadata storage and the
>> keep-alive mechanism of the system to Zookeeper. Since this part is a
>> replacement of basic components, there is a transition, which will switch
>> to zk after the code abstraction is completed. and anyone interested can
>> pay attention to this branch.
>>
>> 3. Development tubemq-manager node:
>> This part is also carried out online, refer to the branch TUBEMQ-421. The
>> requirement of this part is to be an independent management node that spans
>> multiple TubeMQ clusters to facilitate system operation and maintenance.
>>
>> As the related changes are relatively large work, we are going to release
>> the version after the rename of InLong is completed. So, for users of
>> TubeMQ 0.8.0 version, there is a problem that needs to be paid attention
>> to, a bug was recently discovered [2], which affects the information query
>> of webAPI. Before the version is released, please refer to the issue[2] and
>> fix it self:
>>
>> 1.
>> https://issues.apache.org/jira/projects/INFRA/issues/INFRA-21558?filter=allopenissues
>> 2.
>> https://issues.apache.org/jira/projects/TUBEMQ/issues/TUBEMQ-577?filter=doneissues
>>
>> If you have any questions, feedback is welcome.
>>
>> Thanks all!
>>
>>
>>
Re: [Monthly report -- 20210528] Project progress feedback
Posted by Goson zhang <go...@apache.org>.
Hi all:
Recently, we are going to make code and document changes in accordance with
InLong’s adjustment plan, and related PRs merge are temporarily frozen,
sorry!
We hope that the adjusted project can better help those in need
Thanks!
Goson zhang <go...@apache.org> 于2021年5月28日周五 下午4:18写道：
> Sorry, when the translation content is too long, I am not sure whether the
> translation software can understand what I want to say.
>
> In general, the project is gradually attracting people who really pay
> attention and use it, and the project will be adjusted from next month.
>
> Thanks!
>
> Goson zhang <go...@apache.org> 于2021年5月28日周五 下午4:12写道：
>
>> Hello everyone:
>>
>> Summarize the recent situation:
>> 1. Branch 570: now it has entered the testing phase, after this content
>> is launched, the readability and scalability of Web APIs and metadata
>> management will be more better, which is convenient for subsequent feature
>> expansion; due to the compatibility of previous versions, the old version
>> of the API and the underlying BDB data storage classes are still retained,
>> although these old APIs and storage formats are somewhat obsolete;
>>
>> 2. Branch 25: pure Go language SDK, compared with the previous stage, the
>> contributors of this module have already started actual code contributions.
>> If you are interested in Go language implementation and want to
>> participate, you can pay attention to its issue.
>>
>> 3. The main body of InLong will start to move next month: thanks mentor @Justin,
>> @JB have prepared the basic environment of the project. Everyone may pay
>> attention that InLong's code and website content have not been adjusted
>> according to the name change (maybe the people involved in this project are
>> asleep), and someone who chooses to contribute to this problem. First of
>> all, thank contributors @RocMarshal and @leven-space for finding this
>> problem and Initiated an improvement; considering that the changes are too
>> large, we will release it when we are ready, and track the content of each
>> improvement through INLONG-613 and INLONG-614, until all the content is
>> prepared on the branch, and then merged into the project master.
>>
>> 4. A code contribution Tips：when we contribute, we must consider the
>> issue of originality and respect for originality, when we contribute code,
>> if we directly quote external code, we need to declare in the LICENSE and
>> NOTICE of the project, which files are quoted from where, or else it will
>> form infringement; as we directly quote external codes, the LICENSE and
>> NOTICE of the ontology project will expand, this result will make people
>> feel that the project is a hodgepodge. TubeMQ did not consider this issue
>> at first, now we will reduce the direct quotation of the source code of
>> external projects, so we should be as original as possible when
>> contributing code.
>>
>> The last, after the metadata management transformation is completed, in
>> addition to switching the BDB storage module, we will also renovate some
>> old implementations. If you see some bad implementations, please feel free
>> to contribute.
>>
>> Thanks all!
>>
>>
>> ---------- Forwarded message ---------
>> 发件人： Goson zhang <go...@apache.org>
>> Date: 2021年4月30日周五 上午9:46
>> Subject: [Monthly report -- 20210430] Project progress feedback
>> To: <de...@inlong.apache.org>
>>
>>
>> Hello everyone:
>>
>>
>> Recent project progress:
>> 1. Branch 570 has completed the refactoring of the Web APIs: about 80
>> APIs have been adjusted according to the new plan, next, the application
>> logic MetaDataManager class of metadata will be adjusted. After adjustments
>> are finished, the tests will be performed, including unit tests,
>> integration test, compatibility test, and verification are passed, and
>> then the document is written, finally merged into the main branch. After
>> the main line branch is merged, the development branch of the metadata
>> removal BDB component will be started.
>>
>> 2. The SDK of pure Go language has also been assigned(INLONG-25): A man
>> who is concerned about the project and willing to contribute to our project
>> has done an analysis and started the code implementation. The charm of the
>> open source community is that it is as if a seed has been planted, and it
>> begins to sprout and grow without knowing it.
>>
>> 3. The InLong project is slowly gathering resources, and an initial
>> version will be released as soon as possible: since rename took nearly 4
>> months from the time the application was filed to the final implementation,
>> which was far more than expected, so, the resources gathered in the early
>> stage, need to gradually join in, but don't worry, things are changing.
>>
>> By the way, I saw that the latest version of Kafka has removed the
>> zookeeper, great! TubeMQ has removed zookeeper from the core logic around
>> 2017. But now to comply with Apache's LICENSE specification, we will also
>> consider supporting metadata storage components including Zookeeper :).
>>
>> That's it, happy May Day, everyone!
>>
>> Thanks!
>>
>>
>> ---------- Forwarded message ---------
>> 发件人： Goson zhang <go...@apache.org>
>> Date: 2021年3月24日周三 上午10:57
>> Subject: [Monthly report] Project progress feedback
>> To: <de...@tubemq.apache.org>
>>
>>
>> Hello everyone:
>>
>> The community of the project has been a bit quiet recently, not everyone
>> is asleep, we are dealing with the following content:
>>
>> 1. The content preparation of the rename project:
>> According to our previous discussion of renaming, our mentor has
>> submitted a renaming Jira[1] (thanks to mentor JB), we need to organize the
>> relevant project content before the implementation of the renaming,
>> including the new project homepage, Logo, other open source components, etc.
>> Please wait, it is expected that the overall content of the project will
>> be updated after the name change is completed at the end of March, or early
>> April if the rename operation delays.
>>
>> 2. Metadata store component transformation:
>> This part is performing online, refer to the branch TUBEMQ-570. Due to
>> the license issue of BDB, we need to switch the metadata storage and the
>> keep-alive mechanism of the system to Zookeeper. Since this part is a
>> replacement of basic components, there is a transition, which will switch
>> to zk after the code abstraction is completed. and anyone interested can
>> pay attention to this branch.
>>
>> 3. Development tubemq-manager node:
>> This part is also carried out online, refer to the branch TUBEMQ-421. The
>> requirement of this part is to be an independent management node that spans
>> multiple TubeMQ clusters to facilitate system operation and maintenance.
>>
>> As the related changes are relatively large work, we are going to release
>> the version after the rename of InLong is completed. So, for users of
>> TubeMQ 0.8.0 version, there is a problem that needs to be paid attention
>> to, a bug was recently discovered [2], which affects the information query
>> of webAPI. Before the version is released, please refer to the issue[2] and
>> fix it self:
>>
>> 1.
>> https://issues.apache.org/jira/projects/INFRA/issues/INFRA-21558?filter=allopenissues
>> 2.
>> https://issues.apache.org/jira/projects/TUBEMQ/issues/TUBEMQ-577?filter=doneissues
>>
>> If you have any questions, feedback is welcome.
>>
>> Thanks all!
>>
>>
>>
Re: [Monthly report -- 20210528] Project progress feedback
Posted by Goson zhang <go...@apache.org>.
Sorry, when the translation content is too long, I am not sure whether the
translation software can understand what I want to say.
In general, the project is gradually attracting people who really pay
attention and use it, and the project will be adjusted from next month.
Thanks!
Goson zhang <go...@apache.org> 于2021年5月28日周五 下午4:12写道：
> Hello everyone:
>
> Summarize the recent situation:
> 1. Branch 570: now it has entered the testing phase, after this content is
> launched, the readability and scalability of Web APIs and metadata
> management will be more better, which is convenient for subsequent feature
> expansion; due to the compatibility of previous versions, the old version
> of the API and the underlying BDB data storage classes are still retained,
> although these old APIs and storage formats are somewhat obsolete;
>
> 2. Branch 25: pure Go language SDK, compared with the previous stage, the
> contributors of this module have already started actual code contributions.
> If you are interested in Go language implementation and want to
> participate, you can pay attention to its issue.
>
> 3. The main body of InLong will start to move next month: thanks mentor @Justin,
> @JB have prepared the basic environment of the project. Everyone may pay
> attention that InLong's code and website content have not been adjusted
> according to the name change (maybe the people involved in this project are
> asleep), and someone who chooses to contribute to this problem. First of
> all, thank contributors @RocMarshal and @leven-space for finding this
> problem and Initiated an improvement; considering that the changes are too
> large, we will release it when we are ready, and track the content of each
> improvement through INLONG-613 and INLONG-614, until all the content is
> prepared on the branch, and then merged into the project master.
>
> 4. A code contribution Tips：when we contribute, we must consider the issue
> of originality and respect for originality, when we contribute code, if we
> directly quote external code, we need to declare in the LICENSE and NOTICE
> of the project, which files are quoted from where, or else it will form
> infringement; as we directly quote external codes, the LICENSE and NOTICE
> of the ontology project will expand, this result will make people feel that
> the project is a hodgepodge. TubeMQ did not consider this issue at first,
> now we will reduce the direct quotation of the source code of external
> projects, so we should be as original as possible when contributing code.
>
> The last, after the metadata management transformation is completed, in
> addition to switching the BDB storage module, we will also renovate some
> old implementations. If you see some bad implementations, please feel free
> to contribute.
>
> Thanks all!
>
>
> ---------- Forwarded message ---------
> 发件人： Goson zhang <go...@apache.org>
> Date: 2021年4月30日周五 上午9:46
> Subject: [Monthly report -- 20210430] Project progress feedback
> To: <de...@inlong.apache.org>
>
>
> Hello everyone:
>
>
> Recent project progress:
> 1. Branch 570 has completed the refactoring of the Web APIs: about 80 APIs
> have been adjusted according to the new plan, next, the application logic
> MetaDataManager class of metadata will be adjusted. After adjustments are
> finished, the tests will be performed, including unit tests, integration
> test, compatibility test, and verification are passed, and then the
> document is written, finally merged into the main branch. After the main
> line branch is merged, the development branch of the metadata removal BDB
> component will be started.
>
> 2. The SDK of pure Go language has also been assigned(INLONG-25): A man
> who is concerned about the project and willing to contribute to our project
> has done an analysis and started the code implementation. The charm of the
> open source community is that it is as if a seed has been planted, and it
> begins to sprout and grow without knowing it.
>
> 3. The InLong project is slowly gathering resources, and an initial
> version will be released as soon as possible: since rename took nearly 4
> months from the time the application was filed to the final implementation,
> which was far more than expected, so, the resources gathered in the early
> stage, need to gradually join in, but don't worry, things are changing.
>
> By the way, I saw that the latest version of Kafka has removed the
> zookeeper, great! TubeMQ has removed zookeeper from the core logic around
> 2017. But now to comply with Apache's LICENSE specification, we will also
> consider supporting metadata storage components including Zookeeper :).
>
> That's it, happy May Day, everyone!
>
> Thanks!
>
>
> ---------- Forwarded message ---------
> 发件人： Goson zhang <go...@apache.org>
> Date: 2021年3月24日周三 上午10:57
> Subject: [Monthly report] Project progress feedback
> To: <de...@tubemq.apache.org>
>
>
> Hello everyone:
>
> The community of the project has been a bit quiet recently, not everyone
> is asleep, we are dealing with the following content:
>
> 1. The content preparation of the rename project:
> According to our previous discussion of renaming, our mentor has submitted
> a renaming Jira[1] (thanks to mentor JB), we need to organize the relevant
> project content before the implementation of the renaming, including the
> new project homepage, Logo, other open source components, etc.
> Please wait, it is expected that the overall content of the project will
> be updated after the name change is completed at the end of March, or early
> April if the rename operation delays.
>
> 2. Metadata store component transformation:
> This part is performing online, refer to the branch TUBEMQ-570. Due to the
> license issue of BDB, we need to switch the metadata storage and the
> keep-alive mechanism of the system to Zookeeper. Since this part is a
> replacement of basic components, there is a transition, which will switch
> to zk after the code abstraction is completed. and anyone interested can
> pay attention to this branch.
>
> 3. Development tubemq-manager node:
> This part is also carried out online, refer to the branch TUBEMQ-421. The
> requirement of this part is to be an independent management node that spans
> multiple TubeMQ clusters to facilitate system operation and maintenance.
>
> As the related changes are relatively large work, we are going to release
> the version after the rename of InLong is completed. So, for users of
> TubeMQ 0.8.0 version, there is a problem that needs to be paid attention
> to, a bug was recently discovered [2], which affects the information query
> of webAPI. Before the version is released, please refer to the issue[2] and
> fix it self:
>
> 1.
> https://issues.apache.org/jira/projects/INFRA/issues/INFRA-21558?filter=allopenissues
> 2.
> https://issues.apache.org/jira/projects/TUBEMQ/issues/TUBEMQ-577?filter=doneissues
>
> If you have any questions, feedback is welcome.
>
> Thanks all!
>
>
>
[Monthly report -- 20210528] Project progress feedback
Posted by Goson zhang <go...@apache.org>.
Hello everyone:
Summarize the recent situation:
1. Branch 570: now it has entered the testing phase, after this content is
launched, the readability and scalability of Web APIs and metadata
management will be more better, which is convenient for subsequent feature
expansion; due to the compatibility of previous versions, the old version
of the API and the underlying BDB data storage classes are still retained,
although these old APIs and storage formats are somewhat obsolete;
2. Branch 25: pure Go language SDK, compared with the previous stage, the
contributors of this module have already started actual code contributions.
If you are interested in Go language implementation and want to
participate, you can pay attention to its issue.
3. The main body of InLong will start to move next month: thanks
mentor @Justin,
@JB have prepared the basic environment of the project. Everyone may pay
attention that InLong's code and website content have not been adjusted
according to the name change (maybe the people involved in this project are
asleep), and someone who chooses to contribute to this problem. First of
all, thank contributors @RocMarshal and @leven-space for finding this
problem and Initiated an improvement; considering that the changes are too
large, we will release it when we are ready, and track the content of each
improvement through INLONG-613 and INLONG-614, until all the content is
prepared on the branch, and then merged into the project master.
4. A code contribution Tips：when we contribute, we must consider the issue
of originality and respect for originality, when we contribute code, if we
directly quote external code, we need to declare in the LICENSE and NOTICE
of the project, which files are quoted from where, or else it will form
infringement; as we directly quote external codes, the LICENSE and NOTICE
of the ontology project will expand, this result will make people feel that
the project is a hodgepodge. TubeMQ did not consider this issue at first,
now we will reduce the direct quotation of the source code of external
projects, so we should be as original as possible when contributing code.
The last, after the metadata management transformation is completed, in
addition to switching the BDB storage module, we will also renovate some
old implementations. If you see some bad implementations, please feel free
to contribute.
Thanks all!
---------- Forwarded message ---------
发件人： Goson zhang <go...@apache.org>
Date: 2021年4月30日周五 上午9:46
Subject: [Monthly report -- 20210430] Project progress feedback
To: <de...@inlong.apache.org>
Hello everyone:
Recent project progress:
1. Branch 570 has completed the refactoring of the Web APIs: about 80 APIs
have been adjusted according to the new plan, next, the application logic
MetaDataManager class of metadata will be adjusted. After adjustments are
finished, the tests will be performed, including unit tests, integration
test, compatibility test, and verification are passed, and then the
document is written, finally merged into the main branch. After the main
line branch is merged, the development branch of the metadata removal BDB
component will be started.
2. The SDK of pure Go language has also been assigned(INLONG-25): A man who
is concerned about the project and willing to contribute to our project has
done an analysis and started the code implementation. The charm of the open
source community is that it is as if a seed has been planted, and it begins
to sprout and grow without knowing it.
3. The InLong project is slowly gathering resources, and an initial version
will be released as soon as possible: since rename took nearly 4 months
from the time the application was filed to the final implementation, which
was far more than expected, so, the resources gathered in the early stage,
need to gradually join in, but don't worry, things are changing.
By the way, I saw that the latest version of Kafka has removed the
zookeeper, great! TubeMQ has removed zookeeper from the core logic around
2017. But now to comply with Apache's LICENSE specification, we will also
consider supporting metadata storage components including Zookeeper :).
That's it, happy May Day, everyone!
Thanks!
---------- Forwarded message ---------
发件人： Goson zhang <go...@apache.org>
Date: 2021年3月24日周三 上午10:57
Subject: [Monthly report] Project progress feedback
To: <de...@tubemq.apache.org>
Hello everyone:
The community of the project has been a bit quiet recently, not everyone is
asleep, we are dealing with the following content:
1. The content preparation of the rename project:
According to our previous discussion of renaming, our mentor has submitted
a renaming Jira[1] (thanks to mentor JB), we need to organize the relevant
project content before the implementation of the renaming, including the
new project homepage, Logo, other open source components, etc.
Please wait, it is expected that the overall content of the project will be
updated after the name change is completed at the end of March, or early
April if the rename operation delays.
2. Metadata store component transformation:
This part is performing online, refer to the branch TUBEMQ-570. Due to the
license issue of BDB, we need to switch the metadata storage and the
keep-alive mechanism of the system to Zookeeper. Since this part is a
replacement of basic components, there is a transition, which will switch
to zk after the code abstraction is completed. and anyone interested can
pay attention to this branch.
3. Development tubemq-manager node:
This part is also carried out online, refer to the branch TUBEMQ-421. The
requirement of this part is to be an independent management node that spans
multiple TubeMQ clusters to facilitate system operation and maintenance.
As the related changes are relatively large work, we are going to release
the version after the rename of InLong is completed. So, for users of
TubeMQ 0.8.0 version, there is a problem that needs to be paid attention
to, a bug was recently discovered [2], which affects the information query
of webAPI. Before the version is released, please refer to the issue[2] and
fix it self:
1.
https://issues.apache.org/jira/projects/INFRA/issues/INFRA-21558?filter=allopenissues
2.
https://issues.apache.org/jira/projects/TUBEMQ/issues/TUBEMQ-577?filter=doneissues
If you have any questions, feedback is welcome.
Thanks all!
[Monthly report -- 20210430] Project progress feedback
Posted by Goson zhang <go...@apache.org>.
Hello everyone:
Recent project progress:
1. Branch 570 has completed the refactoring of the Web APIs: about 80 APIs
have been adjusted according to the new plan, next, the application logic
MetaDataManager class of metadata will be adjusted. After adjustments are
finished, the tests will be performed, including unit tests, integration
test, compatibility test, and verification are passed, and then the
document is written, finally merged into the main branch. After the main
line branch is merged, the development branch of the metadata removal BDB
component will be started.
2. The SDK of pure Go language has also been assigned(INLONG-25): A man who
is concerned about the project and willing to contribute to our project has
done an analysis and started the code implementation. The charm of the open
source community is that it is as if a seed has been planted, and it begins
to sprout and grow without knowing it.
3. The InLong project is slowly gathering resources, and an initial version
will be released as soon as possible: since rename took nearly 4 months
from the time the application was filed to the final implementation, which
was far more than expected, so, the resources gathered in the early stage,
need to gradually join in, but don't worry, things are changing.
By the way, I saw that the latest version of Kafka has removed the
zookeeper, great! TubeMQ has removed zookeeper from the core logic around
2017. But now to comply with Apache's LICENSE specification, we will also
consider supporting metadata storage components including Zookeeper :).
That's it, happy May Day, everyone!
Thanks!
---------- Forwarded message ---------
发件人： Goson zhang <go...@apache.org>
Date: 2021年3月24日周三 上午10:57
Subject: [Monthly report] Project progress feedback
To: <de...@tubemq.apache.org>
Hello everyone:
The community of the project has been a bit quiet recently, not everyone is
asleep, we are dealing with the following content:
1. The content preparation of the rename project:
According to our previous discussion of renaming, our mentor has submitted
a renaming Jira[1] (thanks to mentor JB), we need to organize the relevant
project content before the implementation of the renaming, including the
new project homepage, Logo, other open source components, etc.
Please wait, it is expected that the overall content of the project will be
updated after the name change is completed at the end of March, or early
April if the rename operation delays.
2. Metadata store component transformation:
This part is performing online, refer to the branch TUBEMQ-570. Due to the
license issue of BDB, we need to switch the metadata storage and the
keep-alive mechanism of the system to Zookeeper. Since this part is a
replacement of basic components, there is a transition, which will switch
to zk after the code abstraction is completed. and anyone interested can
pay attention to this branch.
3. Development tubemq-manager node:
This part is also carried out online, refer to the branch TUBEMQ-421. The
requirement of this part is to be an independent management node that spans
multiple TubeMQ clusters to facilitate system operation and maintenance.
As the related changes are relatively large work, we are going to release
the version after the rename of InLong is completed. So, for users of
TubeMQ 0.8.0 version, there is a problem that needs to be paid attention
to, a bug was recently discovered [2], which affects the information query
of webAPI. Before the version is released, please refer to the issue[2] and
fix it self:
1.
https://issues.apache.org/jira/projects/INFRA/issues/INFRA-21558?filter=allopenissues
2.
https://issues.apache.org/jira/projects/TUBEMQ/issues/TUBEMQ-577?filter=doneissues
If you have any questions, feedback is welcome.
Thanks all!
[Echo, i'm here] How to join the TubeMQ community to contribute?
Posted by Goson zhang <go...@apache.org>.
In some technical exchanges, someone mentioned that I am very interested in
your project, apart from using your project, we also want to participate in
the development of the project. If we want to work on this project
together, what features can you give me to do?, or where should I start?
For this question, I look at it like this:
First of all, we very much hope that anyone outside the original team
participates and joins the project. A NB project must be widely known by
everyone and familiar with its principles. The Apache community is an open
community, more people participate, more people come to join the project
management, not just only the original team managing the project.
Secondly, I think we all need to understand each other about the same
content: our project has completely open sourced the code and published
documents in accordance with Apache’s rules, but for us, you are the side
that we need to know and understand. We need to experience what you see
through your contributions, and make further interactions and exchanges
through contributions, so that I know what features we can do together. We
do not limit what you want to do or not.
As long as you like it, as long as you feel that the project needs
improvement, you can directly raise an issue, put forward your ideas for
discussion, then determine the plan, and then modify it.
The content of these contributions is not limited to the code. Any form of
contribution is welcome. You can start with simple content, such as:
• Typos or formatting corrections
• Document supplement and improvement
• Answer and solve problems
• Maintain official website
• Related articles, practical experience
• Test case supplement
• Fix bugs
• Complete functions and provide new features
• Participate in new feature discussion and code review
• Multi-language version contribution
If it is code, I personally think it would be better to target a module
first, and then gradually expand it. Let me give a few examples:
1. Optimize the current implementation:
TUBEMQ-586 Optimize the implementation of the PartitionExt class
TUBEMQ-585 Optimize the implementation of RmtDataCache class
2. Add new functions:
TUBEMQ-25 Go SDK support for TubeMQ
TUBEMQ-588 C/C++ SDK supports production-side business logic
TUBEMQ-587 Add client-side metrics statistics
TUBEMQ-589 Add Broker's metric statistics
3. Optimize the existing features:
TUBEMQ-591 ZkOffsetStorage module improvements
TUBEMQ-590 Optimize the implementation of DefaultLoadBalancer class
Next, I will regularly post some of the ideas I see on the issue, so that
anyoe who wants to contribute can claim these issues.
Welcome everyone to build together!
Thanks!!
Goson zhang <go...@apache.org> 于2021年3月30日周二 下午5:40写道：
> I don’t know how many people are following this project, and whether you
> have ideas and time to participate in the development of the new
> requirements of the project. So I yelled towards the sea.
>
> I am refactoring the metadata storage part of TubeMQ in the branch
> TUBEMQ-570, you can pay attention to the modification of this branch,
> provide your suggestions and amendments at any time, directly submit your
> issue and pr (if any)
>
> The project's master content has been deposited for many years, it is
> difficult to find some bugs, although some places are not satisfactory.
>
> Thanks!
>
> ---------- Forwarded message ---------
> 发件人： Goson zhang <go...@apache.org>
> Date: 2021年3月24日周三 上午10:57
> Subject: [Monthly report] Project progress feedback
> To: <de...@tubemq.apache.org>
>
>
> Hello everyone:
>
> The community of the project has been a bit quiet recently, not everyone
> is asleep, we are dealing with the following content:
>
> 1. The content preparation of the rename project:
> According to our previous discussion of renaming, our mentor has submitted
> a renaming Jira[1] (thanks to mentor JB), we need to organize the relevant
> project content before the implementation of the renaming, including the
> new project homepage, Logo, other open source components, etc.
> Please wait, it is expected that the overall content of the project will
> be updated after the name change is completed at the end of March, or early
> April if the rename operation delays.
>
> 2. Metadata store component transformation:
> This part is performing online, refer to the branch TUBEMQ-570. Due to the
> license issue of BDB, we need to switch the metadata storage and the
> keep-alive mechanism of the system to Zookeeper. Since this part is a
> replacement of basic components, there is a transition, which will switch
> to zk after the code abstraction is completed. and anyone interested can
> pay attention to this branch.
>
> 3. Development tubemq-manager node:
> This part is also carried out online, refer to the branch TUBEMQ-421. The
> requirement of this part is to be an independent management node that spans
> multiple TubeMQ clusters to facilitate system operation and maintenance.
>
> As the related changes are relatively large work, we are going to release
> the version after the rename of InLong is completed. So, for users of
> TubeMQ 0.8.0 version, there is a problem that needs to be paid attention
> to, a bug was recently discovered [2], which affects the information query
> of webAPI. Before the version is released, please refer to the issue[2] and
> fix it self:
>
> 1.
> https://issues.apache.org/jira/projects/INFRA/issues/INFRA-21558?filter=allopenissues
> 2.
> https://issues.apache.org/jira/projects/TUBEMQ/issues/TUBEMQ-577?filter=doneissues
>
> If you have any questions, feedback is welcome.
>
> Thanks all!
>
>
>
[Echo, i'm here] Are there any one who are interested in the TubeMQ project?
Posted by Goson zhang <go...@apache.org>.
I don’t know how many people are following this project, and whether you
have ideas and time to participate in the development of the new
requirements of the project. So I yelled towards the sea.
I am refactoring the metadata storage part of TubeMQ in the branch
TUBEMQ-570, you can pay attention to the modification of this branch,
provide your suggestions and amendments at any time, directly submit your
issue and pr (if any)
The project's master content has been deposited for many years, it is
difficult to find some bugs, although some places are not satisfactory.
Thanks!
---------- Forwarded message ---------
发件人： Goson zhang <go...@apache.org>
Date: 2021年3月24日周三 上午10:57
Subject: [Monthly report] Project progress feedback
To: <de...@tubemq.apache.org>
Hello everyone:
The community of the project has been a bit quiet recently, not everyone is
asleep, we are dealing with the following content:
1. The content preparation of the rename project:
According to our previous discussion of renaming, our mentor has submitted
a renaming Jira[1] (thanks to mentor JB), we need to organize the relevant
project content before the implementation of the renaming, including the
new project homepage, Logo, other open source components, etc.
Please wait, it is expected that the overall content of the project will be
updated after the name change is completed at the end of March, or early
April if the rename operation delays.
2. Metadata store component transformation:
This part is performing online, refer to the branch TUBEMQ-570. Due to the
license issue of BDB, we need to switch the metadata storage and the
keep-alive mechanism of the system to Zookeeper. Since this part is a
replacement of basic components, there is a transition, which will switch
to zk after the code abstraction is completed. and anyone interested can
pay attention to this branch.
3. Development tubemq-manager node:
This part is also carried out online, refer to the branch TUBEMQ-421. The
requirement of this part is to be an independent management node that spans
multiple TubeMQ clusters to facilitate system operation and maintenance.
As the related changes are relatively large work, we are going to release
the version after the rename of InLong is completed. So, for users of
TubeMQ 0.8.0 version, there is a problem that needs to be paid attention
to, a bug was recently discovered [2], which affects the information query
of webAPI. Before the version is released, please refer to the issue[2] and
fix it self:
1.
https://issues.apache.org/jira/projects/INFRA/issues/INFRA-21558?filter=allopenissues
2.
https://issues.apache.org/jira/projects/TUBEMQ/issues/TUBEMQ-577?filter=doneissues
If you have any questions, feedback is welcome.
Thanks all!