[VOTE] Thrift 0.6.1 RC0

[Jake Farrell]

All,

I propose that we accept
http://people.apache.org/~jfarrell/thrift/0.6.1/thrift-0.6.1-rc0.tar.gz as the
official Thrift 0.6.1 release. There where a couple small bug fixes against
the  0.6.x branch and this is mainly to get the java library published into 
the apache maven repository.

I generated this tarball by checking out
https://svn.apache.org/repos/asf/thrift/branches/0.6.x and running
"./bootstrap.sh && ./configure && make dist".

The GPG signature can be found at: 
http://people.apache.org/~jfarrell/thrift/0.6.1/thrift-0.6.1-rc0.tar.gz.asc.
It has an MD5 sum of dcd9d2d39aa22b615dd5c5ef2d7b7cfb.

The java library can be found at:
http://people.apache.org/~jfarrell/thrift/0.6.1/lib/java 
or
https://repository.apache.org/content/repositories/orgapachethrift-107
It has an MD5 sum of 21bf7163d03bff22ca0b6598ae3f05e0.

Please download, verify sig/sum, and install/test the libraries of your
choice.

This vote closes in 72 hours.

-Jake

[VOTE] Thrift 0.6.1 RC1

[Jake Farrell]

Closing RC0 due to the issues Roger found and proposing RC1 
as the new 0.6.1 candidate available at
http://people.apache.org/~jfarrell/thrift/0.6.1/thrift-0.6.1-rc1.tar.gz. 
RC0  was a set of small bug fixes against the  0.6.x branch and this 
release is mainly to get the java library published into the apache maven 
repository. On top of the RC0 this includes the javascript test 
case fix as well as adding the java build.properties file.

I generated this tarball by checking out 
https://svn.apache.org/repos/asf/thrift/branches/0.6.x and running 
"./bootstrap.sh && ./configure && make dist".

The GPG signature can be found at:
http://people.apache.org/~jfarrell/thrift/0.6.1/thrift-0.6.1-rc1.tar.gz.asc
It has an MD5 sum of e1ec722d5f38077a23a32c4de4d4ce94.

The java library can be found at:
http://people.apache.org/~jfarrell/thrift/0.6.1/lib/java
or
https://repository.apache.org/content/repositories/orgapachethrift-110
It has an MD5 sum of 55307eee5fce3903537a3df45e47c0a2.

Please download, verify sig/sum, and install/test the libraries of 
your choice.

This vote closes in 72 hours.

-Jake



On Apr 20, 2011, at 2:14 PM, Roger Meier wrote:

> Great job!
> 
> But there's a little issue probably worth to fix
> 
> build.properties is missing within the thrift-0.6.1-rc0.tar.gz:
> 
> https://svn.apache.org/repos/asf/thrift/branches/0.6.x/lib/java/build.proper
> ties
> 
> to be added as EXTRA_DIST target:
> 
> Index: lib/java/Makefile.am
> ===
> --- lib/java/Makefile.am(revision 1095483)
> +++ lib/java/Makefile.am(working copy)
> @@ -17,7 +17,7 @@
> # under the License.
> #
> 
> -EXTRA_DIST = build.xml src test
> +EXTRA_DIST = build.properties build.xml src test
> 
> export CLASSPATH
> ===
> 
> -roger
> 
> -Ursprüngliche Nachricht-
> Von: Jake Luciani [mailto:jak...@gmail.com] 
> Gesendet: Mittwoch, 20. April 2011 19:38
> An: dev@thrift.apache.org
> Betreff: Re: [VOTE] Thrift 0.6.1 RC0
> 
> +1
> 
> On Tue, Apr 19, 2011 at 6:41 PM, Jake Farrell  wrote:
> 
>> All,
>> 
>> I propose that we accept
>> http://people.apache.org/~jfarrell/thrift/0.6.1/thrift-0.6.1-rc0.tar.g
>> z as the official Thrift 0.6.1 release. There where a couple small bug 
>> fixes against the  0.6.x branch and this is mainly to get the java 
>> library published into the apache maven repository.
>> 
>> I generated this tarball by checking out 
>> https://svn.apache.org/repos/asf/thrift/branches/0.6.x and running 
>> "./bootstrap.sh && ./configure && make dist".
>> 
>> The GPG signature can be found at:
>> http://people.apache.org/~jfarrell/thrift/0.6.1/thrift-0.6.1-rc0.tar.g
>> z.asc
>> .
>> It has an MD5 sum of dcd9d2d39aa22b615dd5c5ef2d7b7cfb.
>> 
>> The java library can be found at:
>> http://people.apache.org/~jfarrell/thrift/0.6.1/lib/java
>> or
>> https://repository.apache.org/content/repositories/orgapachethrift-107
>> It has an MD5 sum of 21bf7163d03bff22ca0b6598ae3f05e0.
>> 
>> Please download, verify sig/sum, and install/test the libraries of 
>> your choice.
>> 
>> This vote closes in 72 hours.
>> 
>> -Jake
> 
> 
> 
> 
> --
> http://twitter.com/tjake
> 

Re: [VOTE] Thrift 0.6.1 RC1

[Jake Farrell]

With 5 binding +1s and no -1s the 0.6.1 RC1 vote passes. I'll get 0.6.1 release 
published here shortly


On Apr 22, 2011, at 7:12 AM, Roger Meier wrote:

> +1
> 
> -Ursprüngliche Nachricht-
> Von: Mark Slee [mailto:ms...@fb.com] 
> Gesendet: Donnerstag, 21. April 2011 20:37
> An: dev@thrift.apache.org
> Betreff: RE: [VOTE] Thrift 0.6.1 RC1
> 
> +1
> 
> -Original Message-
> From: Jake Luciani [mailto:jak...@gmail.com]
> Sent: Thursday, April 21, 2011 9:06 AM
> To: dev@thrift.apache.org
> Subject: Re: [VOTE] Thrift 0.6.1 RC1
> 
> +1
> 
> On Thu, Apr 21, 2011 at 11:49 AM, Anthony Molinaro <
> antho...@alumni.caltech.edu> wrote:
> 
>> +1
>> 
>> On Apr 20, 2011, at 3:25 PM, Jake Farrell  wrote:
>> 
>>> Closing RC0 due to the issues Roger found and proposing RC1 as the 
>>> new 0.6.1 candidate available at 
>>> http://people.apache.org/~jfarrell/thrift/0.6.1/thrift-0.6.1-rc1.tar.gz.
>>> RC0  was a set of small bug fixes against the  0.6.x branch and this 
>>> release is mainly to get the java library published into the apache 
>>> maven repository. On top of the RC0 this includes the javascript 
>>> test case fix as well as adding the java build.properties file.
>>> 
>>> I generated this tarball by checking out 
>>> https://svn.apache.org/repos/asf/thrift/branches/0.6.x and running 
>>> "./bootstrap.sh && ./configure && make dist".
>>> 
>>> The GPG signature can be found at:
>>> 
>> http://people.apache.org/~jfarrell/thrift/0.6.1/thrift-0.6.1-rc1.tar.g
>> z.asc
>>> It has an MD5 sum of e1ec722d5f38077a23a32c4de4d4ce94.
>>> 
>>> The java library can be found at:
>>> http://people.apache.org/~jfarrell/thrift/0.6.1/lib/java
>>> or
>>> https://repository.apache.org/content/repositories/orgapachethrift-1
>>> 10 It has an MD5 sum of 55307eee5fce3903537a3df45e47c0a2.
>>> 
>>> Please download, verify sig/sum, and install/test the libraries of 
>>> your choice.
>>> 
>>> This vote closes in 72 hours.
>>> 
>>> -Jake
>>> 
>>> 
>>> 
>>> On Apr 20, 2011, at 2:14 PM, Roger Meier wrote:
>>> 
>>>> Great job!
>>>> 
>>>> But there's a little issue probably worth to fix
>>>> 
>>>> build.properties is missing within the thrift-0.6.1-rc0.tar.gz:
>>>> 
>>>> 
>> https://svn.apache.org/repos/asf/thrift/branches/0.6.x/lib/java/build.
>> proper
>>>> ties
>>>> 
>>>> to be added as EXTRA_DIST target:
>>>> 
>>>> Index: lib/java/Makefile.am
>>>> ===
>>>> --- lib/java/Makefile.am    (revision 1095483)
>>>> +++ lib/java/Makefile.am(working copy)
>>>> @@ -17,7 +17,7 @@
>>>> # under the License.
>>>> #
>>>> 
>>>> -EXTRA_DIST = build.xml src test
>>>> +EXTRA_DIST = build.properties build.xml src test
>>>> 
>>>> export CLASSPATH
>>>> ===
>>>> 
>>>> -roger
>>>> 
>>>> -Ursprüngliche Nachricht-
>>>> Von: Jake Luciani [mailto:jak...@gmail.com]
>>>> Gesendet: Mittwoch, 20. April 2011 19:38
>>>> An: dev@thrift.apache.org
>>>> Betreff: Re: [VOTE] Thrift 0.6.1 RC0
>>>> 
>>>> +1
>>>> 
>>>> On Tue, Apr 19, 2011 at 6:41 PM, Jake Farrell 
>> wrote:
>>>> 
>>>>> All,
>>>>> 
>>>>> I propose that we accept
>>>>> http://people.apache.org/~jfarrell/thrift/0.6.1/thrift-0.6.1-rc0.t
>>>>> ar.g z as the official Thrift 0.6.1 release. There where a couple 
>>>>> small bug fixes against the  0.6.x branch and this is mainly to 
>>>>> get the java library published into the apache maven repository.
>>>>> 
>>>>> I generated this tarball by checking out 
>>>>> https://svn.apache.org/repos/asf/thrift/branches/0.6.x and running 
>>>>> "./bootstrap.sh && ./configure && make dist".
>>>>> 
>>>>> The GPG signature can be found at:
>>>>> http://people.apache.org/~jfarrell/thrift/0.6.1/thrift-0.6.1-rc0.t
>>>>> ar.g
>>>>> z.asc
>>>>> .
>>>>> It has an MD5 sum of dcd9d2d39aa22b615dd5c5ef2d7b7cfb.
>>>>> 
>>>>> The java library can be found at:
>>>>> http://people.apache.org/~jfarrell/thrift/0.6.1/lib/java
>>>>> or
>>>>> https://repository.apache.org/content/repositories/orgapachethrift
>>>>> -107 It has an MD5 sum of 21bf7163d03bff22ca0b6598ae3f05e0.
>>>>> 
>>>>> Please download, verify sig/sum, and install/test the libraries of 
>>>>> your choice.
>>>>> 
>>>>> This vote closes in 72 hours.
>>>>> 
>>>>> -Jake
>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> http://twitter.com/tjake
>>>> 
>>> 
>> 
> 
> 
> 
> --
> http://twitter.com/tjake
> 
> 
> 

Re: Publish Libthrift Javadocs

[Jake Farrell]

You can view a copy of the current 0.6.1 javadoc at 
http://people.apache.org/~jfarrell/thrift/0.6.1/javadoc/


On Apr 27, 2011, at 3:42 PM, Abhishek Kona wrote:

> Is it possible to host the libthrift java-docs on the wiki or on some 
> server.
> 
> -Abhishek Kona
> 

Re: libthrift .swc artifact deployment for flex-mojos users?

[Jake Farrell]

Working on this, will have a patch shortly that will get this lib ready to be 
added into maven along side the java driver


On May 18, 2011, at 4:23 PM, Aron Sogor wrote:

> I think we would welcome help with that :)
> 
> If you willing to take a crack at it we would be happy to help.
> 
> On Wed, May 18, 2011 at 11:00 AM, Florentine, Justin F.
>  wrote:
>> Thanks so much for getting the java implementation deployed to the central
>> Maven repository!  Would it be possible to do the same for the Flex
>> implementation as well?  Here at ESPN we are using flex-mojos to build and
>> manage our Flex builds, and it would be great to no longer have to manage
>> the entry for it in our repository locally.
>> 
>> Thanks!
>> 
>> 

Re: Thrift on Apache Reviewboard

[Jake Farrell]

I commented on the ticket, thanks Diwaker for creating it.



On Jul 5, 2011, at 6:32 PM, Diwaker Gupta wrote:

> Folks,
> 
> I've submitted a request to add Thrift to Apache Reviewboard:
> https://issues.apache.org/jira/browse/INFRA-3752
> 
> It will be great if some of the core Thrift devs (PMC?) could show
> their support on that issue so we can do better code reviews for
> Thrift.
> 
> cheers,
> Diwaker

Re: trouble building the tutorial in java..

[Jake Farrell]

The java library was moved in 6.1 during the integration for maven. The lib is 
now located at lib/java/build/libthrift-0.7.0-snapshot.jar after building. If a 
release flag is set then the -snapshot will not get appended. I've updated the 
readme to reflect these changes. If you have any trouble with this please let 
me know

Jake


On Jul 23, 2011, at 6:42 PM, Gautam Thaker wrote:

> I was able to build thrift-0.6.1 on Fedora 15 without any errors. I have
> run the "cpp" tutorial extensively. But I can't build the java tutorial.
> The README says to check for libthrift.jar, but one was not build when i
> built jar. The "jar" files that I do have are:
> 
> 
> /tmp/thrift-0.6.1/lib/java/build/libthrift-0.6.1-snapshot-javadoc.jar
> /tmp/thrift-0.6.1/lib/java/build/tools/maven-ant-tasks-2.1.3.jar
> /tmp/thrift-0.6.1/lib/java/build/libthrift-0.6.1-snapshot.jar
> /tmp/thrift-0.6.1/lib/java/build/lib/commons-codec-1.3.jar
> /tmp/thrift-0.6.1/lib/java/build/lib/slf4j-api-1.5.8.jar
> /tmp/thrift-0.6.1/lib/java/build/lib/junit-4.4.jar
> /tmp/thrift-0.6.1/lib/java/build/lib/httpcore-4.0.1.jar
> /tmp/thrift-0.6.1/lib/java/build/lib/commons-lang-2.5.jar
> /tmp/thrift-0.6.1/lib/java/build/lib/log4j-1.2.14.jar
> /tmp/thrift-0.6.1/lib/java/build/lib/slf4j-log4j12-1.5.8.jar
> /tmp/thrift-0.6.1/lib/java/build/lib/httpclient-4.0.1.jar
> /tmp/thrift-0.6.1/lib/java/build/lib/commons-logging-1.1.1.jar
> /tmp/thrift-0.6.1/lib/java/build/lib/servlet-api-2.5.jar
> 
> 
> which does not include "libthrift.jar" that is mentioned in the README
> below.
> 
> Any hints welcome.
> 
> Gautam
> 
> 
> Steps for Java tutorial
> ==
> 
> 1) Make sure thrift is compiled, both the compiler and the Java library.
> You should
> be able to verify the following:
> 
> thrift/tutorial/java$ file ../../lib/java/libthrift.jar
> ../../lib/java/libthrift.jar: Zip archive data, at least v1.0 to extract

Re: 0.7 release date

[Jake Farrell]

I can get it started, will bundle and make available this afternoon


On Aug 10, 2011, at 11:52 AM, Bryan Duxbury wrote:

> I keep meaning to get the ball rolling on an RC, but end up working on other
> things. I would be happy to help one of the other committers through the
> release process if they wanted to take the lead.
> 
> On Tue, Aug 9, 2011 at 11:38 PM, Ivan Murashko wrote:
> 
>> Hi all,
>> 
>> Is there any info about ver. 0.7 release? When is it planed?
>> 
>> --
>> Best regards,
>> Ivan
>> 

[VOTE] Release Apache Thrift 0.7.0

[Jake Farrell]

All,

I propose that we accept
http://people.apache.org/~jfarrell/thrift/0.7.0/thrift-0.7.0-rc0.tar.gz
as the official Thrift 0.7.0 release.

I generated this tarball by checking out
https://svn.apache.org/repos/asf/thrift/branches/0.7.x and running
"./bootstrap.sh && ./configure && make dist".

The GPG signature can be found at: 
http://people.apache.org/~jfarrell/thrift/0.7.0/thrift-0.7.0-rc0.tar.gz.asc.
It has an MD5 sum of 8d7a0070a223e59cf6a2d72aa013b3c4.

The java library can be found at:
https://repository.apache.org/content/repositories/orgapachethrift-025/
libthrift-0.7.0.jar has an MD5 sum of 9d82be1cd2f75a6218ff4a4fb1d91015.

The CHANGES list for this release if available at:
http://svn.apache.org/repos/asf/thrift/branches/0.7.x/CHANGES

Please download, verify sig/sum, and install/test the libraries of your
choice.

This vote closes in 72 hours.

-Jake

Re: AW: [VOTE] Release Apache Thrift 0.7.0

[Jake Farrell]

I thought we had taken care of that in 6.1, i'll go ahead and give myself a 
ticket to automate this process. I've updated the versions and placed the 
rc0+versions back up on my site. Thanks everyone for helping test and get this 
out.

-Jake


On Aug 10, 2011, at 6:48 PM, Roger Meier wrote:

> Thanks Jake for preparing the release!
> 
> I have just one open issue... the version info
> Many files contain version information and they have to be updated manually 
> See http://wiki.apache.org/thrift/HowToVersion
> 
> We can probably  add a build.xml to update that version info and cross
> language unit tests.
> 
> -Roger
> 
>> -Ursprüngliche Nachricht-
>> Von: Jake Farrell [mailto:jfarr...@apache.org]
>> Gesendet: Donnerstag, 11. August 2011 00:09
>> An: dev@thrift.apache.org
>> Betreff: [VOTE] Release Apache Thrift 0.7.0
>> 
>> All,
>> 
>> I propose that we accept
>> http://people.apache.org/~jfarrell/thrift/0.7.0/thrift-0.7.0-rc0.tar.gz
>> as the official Thrift 0.7.0 release.
>> 
>> I generated this tarball by checking out
>> https://svn.apache.org/repos/asf/thrift/branches/0.7.x and running
>> "./bootstrap.sh && ./configure && make dist".
>> 
>> The GPG signature can be found at:
>> 
> http://people.apache.org/~jfarrell/thrift/0.7.0/thrift-0.7.0-rc0.tar.gz.asc.
>> It has an MD5 sum of 8d7a0070a223e59cf6a2d72aa013b3c4.
>> 
>> The java library can be found at:
>> https://repository.apache.org/content/repositories/orgapachethrift-025/
>> libthrift-0.7.0.jar has an MD5 sum of 9d82be1cd2f75a6218ff4a4fb1d91015.
>> 
>> The CHANGES list for this release if available at:
>> http://svn.apache.org/repos/asf/thrift/branches/0.7.x/CHANGES
>> 
>> Please download, verify sig/sum, and install/test the libraries of your
> choice.
>> 
>> This vote closes in 72 hours.
>> 
>> -Jake
>> 
> 
> 

Re: AW: [VOTE] Release Apache Thrift 0.7.0

[Jake Farrell]

I thought we had taken care of that in 6.1, i'll go ahead and give myself a 
ticket to automate this process. I've updated the versions and placed the 
rc0+versions back up on my site. Thanks everyone for helping test and get this 
out.

-Jake


On Aug 10, 2011, at 6:48 PM, Roger Meier wrote:

> Thanks Jake for preparing the release!
> 
> I have just one open issue... the version info
> Many files contain version information and they have to be updated manually 
> See http://wiki.apache.org/thrift/HowToVersion
> 
> We can probably  add a build.xml to update that version info and cross
> language unit tests.
> 
> -Roger
> 
>> -Ursprüngliche Nachricht-
>> Von: Jake Farrell [mailto:jfarr...@apache.org]
>> Gesendet: Donnerstag, 11. August 2011 00:09
>> An: dev@thrift.apache.org
>> Betreff: [VOTE] Release Apache Thrift 0.7.0
>> 
>> All,
>> 
>> I propose that we accept
>> http://people.apache.org/~jfarrell/thrift/0.7.0/thrift-0.7.0-rc0.tar.gz
>> as the official Thrift 0.7.0 release.
>> 
>> I generated this tarball by checking out
>> https://svn.apache.org/repos/asf/thrift/branches/0.7.x and running
>> "./bootstrap.sh && ./configure && make dist".
>> 
>> The GPG signature can be found at:
>> 
> http://people.apache.org/~jfarrell/thrift/0.7.0/thrift-0.7.0-rc0.tar.gz.asc.
>> It has an MD5 sum of 8d7a0070a223e59cf6a2d72aa013b3c4.
>> 
>> The java library can be found at:
>> https://repository.apache.org/content/repositories/orgapachethrift-025/
>> libthrift-0.7.0.jar has an MD5 sum of 9d82be1cd2f75a6218ff4a4fb1d91015.
>> 
>> The CHANGES list for this release if available at:
>> http://svn.apache.org/repos/asf/thrift/branches/0.7.x/CHANGES
>> 
>> Please download, verify sig/sum, and install/test the libraries of your
> choice.
>> 
>> This vote closes in 72 hours.
>> 
>> -Jake
>> 
> 
> 

[RESULT]:[VOTE] Release Apache Thrift 0.7.0

[Jake Farrell]

Counting myself we have four +1s with no 0 or -1 votes, the 0.7.0 release 
passes. Great work everyone on this release, I'll get the website updated and 
push out the artifacts. 

-Jake


On Aug 13, 2011, at 12:06 AM, Roger Meier wrote:

> Thanks Jake! Looks good now!
> 
> +1
> 
> -Roger
> 
>> -Ursprüngliche Nachricht-
>> Von: Ilya Maykov [mailto:ivmay...@gmail.com]
>> Gesendet: Donnerstag, 11. August 2011 22:25
>> An: dev@thrift.apache.org
>> Betreff: Re: [VOTE] Release Apache Thrift 0.7.0
>> 
>> Ruby compiler and libraries look good and pass all tests.
>> 
>> +1
>> 
>> -- Ilya
>> 
>> 
>> On Thu, Aug 11, 2011 at 11:48 AM, Bryan Duxbury 
>> wrote:
>> 
>>> I was able to resolve my GPG issues and verified that the compiler and
>>> Java tests run as expected.
>>> 
>>> +1
>>> 
>>> On Wed, Aug 10, 2011 at 3:08 PM, Jake Farrell 
> wrote:
>>> 
>>>> All,
>>>> 
>>>> I propose that we accept
>>>> http://people.apache.org/~jfarrell/thrift/0.7.0/thrift-0.7.0-rc0.tar
>>>> .gz as the official Thrift 0.7.0 release.
>>>> 
>>>> I generated this tarball by checking out
>>>> https://svn.apache.org/repos/asf/thrift/branches/0.7.x and running
>>>> "./bootstrap.sh && ./configure && make dist".
>>>> 
>>>> The GPG signature can be found at:
>>>> 
>>> http://people.apache.org/~jfarrell/thrift/0.7.0/thrift-0.7.0-rc0.tar.g
>>> z.asc
>>>> .
>>>> It has an MD5 sum of 8d7a0070a223e59cf6a2d72aa013b3c4.
>>>> 
>>>> The java library can be found at:
>>>> https://repository.apache.org/content/repositories/orgapachethrift-0
>>>> 25/ libthrift-0.7.0.jar has an MD5 sum of
>>>> 9d82be1cd2f75a6218ff4a4fb1d91015.
>>>> 
>>>> The CHANGES list for this release if available at:
>>>> http://svn.apache.org/repos/asf/thrift/branches/0.7.x/CHANGES
>>>> 
>>>> Please download, verify sig/sum, and install/test the libraries of
>>>> your choice.
>>>> 
>>>> This vote closes in 72 hours.
>>>> 
>>>> -Jake
>>>> 
>>> 
> 

Thrift-0.7.0 Ruby Gem

[Jake Farrell]

As part of the Thrift release process i've added the steps to start uploading 
the ruby client to Rubygems.org. The current release of thrift-0.7.0 is now 
available via 'gem install thrift'. 

-Jake

Re: Some bug with t_cpp_generator::generate_deserialize_container

[Jake Farrell]

If you would like to file a ticket for this issue please do so at 
http://issues.apache.org/jira/browse/thrift and attach the patch with ASF 
inclusion and we will gladly take a look into this.

Thank you
-Jake

On Aug 10, 2011, at 8:01 PM, ftpeng wrote:

> Signed-off-by: ftpeng 
> ---
> compiler/cpp/src/generate/t_cpp_generator.cc |   12 ++--
> 1 files changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/compiler/cpp/src/generate/t_cpp_generator.cc 
> b/compiler/cpp/src/generate/t_cpp_generator.cc
> index 472644e..7e64832 100755
> --- a/compiler/cpp/src/generate/t_cpp_generator.cc
> +++ b/compiler/cpp/src/generate/t_cpp_generator.cc
> @@ -3448,17 +3448,17 @@ void 
> t_cpp_generator::generate_deserialize_container(ofstream& out,
> out <<
>   indent() << "::apache::thrift::protocol::TType " << ktype << ";" << 
> endl <<
>   indent() << "::apache::thrift::protocol::TType " << vtype << ";" << 
> endl <<
> -  indent() << "iprot->readMapBegin(" <<
> +  indent() << "xfer += iprot->readMapBegin(" <<
>ktype << ", " << vtype << ", " << size << ");" << endl;
>   } else if (ttype->is_set()) {
> out <<
>   indent() << "::apache::thrift::protocol::TType " << etype << ";" << 
> endl <<
> -  indent() << "iprot->readSetBegin(" <<
> +  indent() << "xfer += iprot->readSetBegin(" <<
>etype << ", " << size << ");" << endl;
>   } else if (ttype->is_list()) {
> out <<
>   indent() << "::apache::thrift::protocol::TType " << etype << ";" << 
> endl <<
> -  indent() << "iprot->readListBegin(" <<
> +  indent() << "xfer += iprot->readListBegin(" <<
>   etype << ", " << size << ");" << endl;
> if (!use_push) {
>   indent(out) << prefix << ".resize(" << size << ");" << endl;
> @@ -3486,11 +3486,11 @@ void 
> t_cpp_generator::generate_deserialize_container(ofstream& out,
> 
>   // Read container end
>   if (ttype->is_map()) {
> -indent(out) << "iprot->readMapEnd();" << endl;
> +indent(out) << "xfer += iprot->readMapEnd();" << endl;
>   } else if (ttype->is_set()) {
> -indent(out) << "iprot->readSetEnd();" << endl;
> +indent(out) << "xfer += iprot->readSetEnd();" << endl;
>   } else if (ttype->is_list()) {
> -indent(out) << "iprot->readListEnd();" << endl;
> +indent(out) << "xfer += iprot->readListEnd();" << endl;
>   }
> 
>   scope_down(out);
> -- 
> 1.7.6.msysgit.0
> 
> <0001-Fix-bug-generate_deserialize_container.patch>

On Aug 16, 2011, at 8:19 PM, 彭福田 wrote:

> Please fix it
> 
> -邮件原件-
> 发件人: jfarr...@apache.org [mailto:jfarr...@apache.org] 
> 发送时间: 2011年8月17日 01:14
> 收件人: comm...@thrift.apache.org
> 主题: svn commit: r1158383 - /thrift/trunk/lib/rb/Rakefile
> 
> Author: jfarrell
> Date: Tue Aug 16 17:13:41 2011
> New Revision: 1158383
> 
> URL: http://svn.apache.org/viewvc?rev=1158383&view=rev
> Log:
> Thrift-1263: Updating rb client Rakefile to add suport for publishing client 
> to rubygems.org
> Client: Ruby
> Patch: Jfarrell
> 
> Updating Rakefile to remove deprecated functions and add support for 
> publishing to rubgems.org
> 
> 
> 
> Modified:
>thrift/trunk/lib/rb/Rakefile
> 
> Modified: thrift/trunk/lib/rb/Rakefile
> URL: 
> http://svn.apache.org/viewvc/thrift/trunk/lib/rb/Rakefile?rev=1158383&r1=1158382&r2=1158383&view=diff
> ==
> --- thrift/trunk/lib/rb/Rakefile (original)
> +++ thrift/trunk/lib/rb/Rakefile Tue Aug 16 17:13:41 2011
> @@ -19,7 +19,7 @@
> 
> require 'rubygems'
> require 'rake'
> -require 'spec/rake/spectask'
> +require 'rspec/core/rake_task'
> 
> THRIFT = '../../compiler/cpp/thrift'
> 
> @@ -27,14 +27,12 @@ task :default => [:spec]
> 
> task :spec => [:'gen-rb', :realspec]
> 
> -Spec::Rake::SpecTask.new(:realspec) do |t|
> -  t.spec_files = FileList['spec/**/*_spec.rb']
> -  t.spec_opts = ['--color']
> +RSpec::Core::RakeTask.new(:realspec) do |t|
> +  t.rspec_opts = ['--color']
> end
> 
> -Spec::Rake::SpecTask.new(:'spec:rcov') do |t|
> -  t.spec_files = FileList['spec/**/*_spec.rb']
> -  t.spec_opts = ['--color']
> +RSpec::Core::RakeTask.new(:'spec:rcov') do |t|
> +  t.rspec_opts = ['--color']
>   t.rcov = true
>   t.rcov_opts = ['--exclude', '^spec,/gems/']
> end
> @@ -102,3 +100,4 @@ rescue LoadError
> end
>   end
> end
> +
> 

Re: Build failed in Jenkins: Thrift-cpp #152

[Jake Farrell]

Roger
Thoughts on removing the -Wextra flag from the hudson test script to avoid this?

- Jake



On Sep 6, 2011, at 11:40 AM, Apache Jenkins Server wrote:

> See 
> 
> Changes:
> 
> [jfarrell] Thrift-1322: OCaml lib fail to compile: Thrift.ml line 305, int vs 
> int32 mismatch
> Client: OCaml
> 
> Updates the ocaml lib INTERNAL and PROTOCOL error enums to use the correct 
> numeric values
> 
> --
> [...truncated 459 lines...]
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -I/usr/include -I./src 
> -Wall -Wextra -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overflow 
> -Werror -Wall -Wall -Wextra -pedantic -Wno-long-long -Wno-variadic-macros 
> -Wno-overflow -Werror -MT THttpTransport.lo -MD -MP -MF 
> .deps/THttpTransport.Tpo -c src/transport/THttpTransport.cpp -o 
> THttpTransport.o >/dev/null 2>&1
> mv -f .deps/THttpTransport.Tpo .deps/THttpTransport.Plo
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../..  -I/usr/include -I./src -Wall -Wextra -pedantic -Wno-long-long 
> -Wno-variadic-macros -Wno-overflow -Werror -Wall -Wall -Wextra -pedantic 
> -Wno-long-long -Wno-variadic-macros -Wno-overflow -Werror -MT THttpClient.lo 
> -MD -MP -MF .deps/THttpClient.Tpo -c -o THttpClient.lo `test -f 
> 'src/transport/THttpClient.cpp' || echo './'`src/transport/THttpClient.cpp
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -I/usr/include -I./src 
> -Wall -Wextra -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overflow 
> -Werror -Wall -Wall -Wextra -pedantic -Wno-long-long -Wno-variadic-macros 
> -Wno-overflow -Werror -MT THttpClient.lo -MD -MP -MF .deps/THttpClient.Tpo -c 
> src/transport/THttpClient.cpp  -fPIC -DPIC -o .libs/THttpClient.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -I/usr/include -I./src 
> -Wall -Wextra -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overflow 
> -Werror -Wall -Wall -Wextra -pedantic -Wno-long-long -Wno-variadic-macros 
> -Wno-overflow -Werror -MT THttpClient.lo -MD -MP -MF .deps/THttpClient.Tpo -c 
> src/transport/THttpClient.cpp -o THttpClient.o >/dev/null 2>&1
> mv -f .deps/THttpClient.Tpo .deps/THttpClient.Plo
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../..  -I/usr/include -I./src -Wall -Wextra -pedantic -Wno-long-long 
> -Wno-variadic-macros -Wno-overflow -Werror -Wall -Wall -Wextra -pedantic 
> -Wno-long-long -Wno-variadic-macros -Wno-overflow -Werror -MT THttpServer.lo 
> -MD -MP -MF .deps/THttpServer.Tpo -c -o THttpServer.lo `test -f 
> 'src/transport/THttpServer.cpp' || echo './'`src/transport/THttpServer.cpp
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -I/usr/include -I./src 
> -Wall -Wextra -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overflow 
> -Werror -Wall -Wall -Wextra -pedantic -Wno-long-long -Wno-variadic-macros 
> -Wno-overflow -Werror -MT THttpServer.lo -MD -MP -MF .deps/THttpServer.Tpo -c 
> src/transport/THttpServer.cpp  -fPIC -DPIC -o .libs/THttpServer.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -I/usr/include -I./src 
> -Wall -Wextra -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overflow 
> -Werror -Wall -Wall -Wextra -pedantic -Wno-long-long -Wno-variadic-macros 
> -Wno-overflow -Werror -MT THttpServer.lo -MD -MP -MF .deps/THttpServer.Tpo -c 
> src/transport/THttpServer.cpp -o THttpServer.o >/dev/null 2>&1
> mv -f .deps/THttpServer.Tpo .deps/THttpServer.Plo
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../..  -I/usr/include -I./src -Wall -Wextra -pedantic -Wno-long-long 
> -Wno-variadic-macros -Wno-overflow -Werror -Wall -Wall -Wextra -pedantic 
> -Wno-long-long -Wno-variadic-macros -Wno-overflow -Werror -MT TSocket.lo -MD 
> -MP -MF .deps/TSocket.Tpo -c -o TSocket.lo `test -f 
> 'src/transport/TSocket.cpp' || echo './'`src/transport/TSocket.cpp
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -I/usr/include -I./src 
> -Wall -Wextra -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overflow 
> -Werror -Wall -Wall -Wextra -pedantic -Wno-long-long -Wno-variadic-macros 
> -Wno-overflow -Werror -MT TSocket.lo -MD -MP -MF .deps/TSocket.Tpo -c 
> src/transport/TSocket.cpp  -fPIC -DPIC -o .libs/TSocket.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -I/usr/include -I./src 
> -Wall -Wextra -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overflow 
> -Werror -Wall -Wall -Wextra -pedantic -Wno-long-long -Wno-variadic-macros 
> -Wno-overflow -Werror -MT TSocket.lo -MD -MP -MF .deps/TSocket.Tpo -c 
> src/transport/TSocket.cpp -o TSocket.o >/dev/null 2>&1
> mv -f .deps/TSocket.Tpo .deps/TSocket.Plo
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../..  -I/usr/include -I./src -Wall -Wextra -pedantic -Wno-long-long 
> -Wno-variadic-macros -Wno-overflow -Werror -Wall -Wall -Wextra -pedantic 
> -Wno-long-long -Wno-variadic-macros -Wno-overflow -Werror -MT TSSLS

Re: patch for THttpClient.c to support basic authentication and invalid SSL

[Jake Farrell]

Sergio
Thanks for wanting to get involved and help. Please see 
http://wiki.apache.org/thrift/HowToContribute for information on providing 
patches

-Jake



On Sep 20, 2011, at 2:48 PM, Sergio M. Ammirata, Ph.D. wrote:

Here is a patch for the THttpClient class that adds support for basic 
authentication and which allows the use of an invalid SSL when connecting using 
https.

--
Sergio M. Ammirata, Ph.D.

Re: thrift 0.3 for Accumulo

[Jake Farrell]

Adam
I saw that your trunk has Thrift 0.6.1 in its pom, are you not using that 
version or do you need help upgrading to the latest Thrift version? We do not 
want to have any old versions of Thrift in the Apache Maven repo and asked that 
any older copies that where less than version 0.6.1 in the repo be removed. We 
are working hard to make sure that the thrift client libraries are available in 
their native distribution points and up to date so projects, such as Accumulo, 
can can benefit from the latest features and bug fixes. 

If you have to include Thrift 0.3 with your 1.3 branch then you should include 
it as a file in your lib folder and reference it in the pom with system scope. 

- Jake



On Oct 5, 2011, at 4:01 PM, Adam Fuchs wrote:

> Hello Thrift devs,
> 
> The current stable branch of the new incubator podling Accumulo has a
> dependency on Thrift version 0.3. Do you think you could post that version
> to the maven repo? Alternatively, would you mind if we upload a copy?
> 
> Thanks,
> Adam

Re: Build failed in Jenkins: Thrift #293

[Jake Farrell]

i'm looking at this right now, not sure why the ci is failing here


On Oct 7, 2011, at 6:59 PM, Dave Watson wrote:

> Anyone know what's up with this failure?  On my dev box 'make check'
> passes this successfully
> 
>> 
>> Executing Client/Server tests with various generated code directories
>> Servers to be tested: TSimpleServer, TThreadedServer, TThreadPoolServer,
>> TProcessPoolServer, TForkingServer, TNonblockingServer, THttpServer
>> Directories to be tested: gen-py-default, gen-py-slots, gen-py-newstyle,
>> gen-py-newstyleslots, gen-py-dynamic, gen-py-dynamicslots
>> Protocols to be tested: accel, binary, compact
>> Options to be tested: ZLIB(yes/no), SSL(yes/no)
>> 
>> 
>> Test run #1:  (includes gen-py-default) Server=TSimpleServer,
>> Proto=accel,  zlib=False,  SSL=False
>> Testing server TSimpleServer: /usr/bin/python ./TestServer.py
>> --genpydir=gen-py-default --proto=accel --port=9090 TSimpleServer
>> Testing client: /usr/bin/python ./TestClient.py --genpydir=gen-py-default
>> --proto=accel --port=9090
>> Traceback (most recent call last):
>> File "./RunClientServer.py", line 185, in 
>>   runServiceTest(genpydir, try_server, try_proto, options.port,
>> with_zlib, with_ssl)
>> File "./RunClientServer.py", line 136, in runServiceTest
>>   raise Exception("Client subprocess failed, retcode=%d, args: %s" %
>> (ret, ' '.join(cli_args)))
>> Exception: Client subprocess failed, retcode=1, args: /usr/bin/python
>> ./TestClient.py --genpydir=gen-py-default --proto=accel --port=9090
>> FAIL: RunClientServer.py
>> ==
>> 1 of 1 test failed
>> ==
>> make[3]: *** [check-TESTS] Error 1
>> make[3]: Leaving directory
>> `/x1/jenkins/jenkins-slave/workspace/Thrift/thrift/test/py'
>> make[2]: *** [check-am] Error 2
>> make[2]: Leaving directory
>> `/x1/jenkins/jenkins-slave/workspace/Thrift/thrift/test/py'
>> make[1]: *** [check-recursive] Error 1
>> make[1]: Leaving directory
>> `/x1/jenkins/jenkins-slave/workspace/Thrift/thrift/test'
>> make: *** [check-recursive] Error 1
>> Build step 'Execute shell' marked build as failure
>> [TASKS] Skipping publisher since build result is FAILURE
>> [WARNINGS] Skipping publisher since build result is FAILURE
>> Archiving artifacts
>> Updating THRIFT-1384
>> Recording test results
>> Publishing Javadoc
>> 
> 

Re: Thrift logo

[Jake Farrell]

Currently there is not, THRIFT-36 is open for any suggestions

-Jake


On Oct 18, 2011, at 7:59 AM, Mathias Herberts wrote:

> As I was working on my Hadoop World presentation, I was looking for an
> illustration for Thrift but could not find anything suitable.
> 
> Is there such thing as a Thrift logo?
> 
> Mathias.

Re: Build failed in Jenkins: Thrift-Compiler-Windows #178

[Jake Farrell]

If you want to open a new ticket for this and take a look at it that would be 
great, otherwise i'll look at it tonight

-Jake

On Oct 25, 2011, at 3:59 PM, Jens Geyer wrote:

> Hi Jake,
> 
> Is there some action required? Reopen the issue and provide an updated 
> patch?
> 
> I'm just asking, because the issue is closed, but there seems to be an 
> error.
> 
> Jens
> 
> --
> From: "Apache Jenkins Server" 
> Sent: Tuesday, October 25, 2011 12:12 PM
> To: 
> Subject: Build failed in Jenkins: Thrift-Compiler-Windows #178
> 
>> i586-mingw32msvc-g++ -DHAVE_CONFIG_H -I. -I../..  -I./src -DMINGW -Wall -g 
>> -O2 -MT thrift-t_delphi_generator.o -MD -MP -MF 
>> .deps/thrift-t_delphi_generator.Tpo -c -o thrift-t_delphi_generator.o 
>> `test -f 'src/generate/t_delphi_generator.cc' || echo 
>> './'`src/generate/t_delphi_generator.cc
>> src/generate/t_delphi_generator.cc:780: error: integer constant is too 
>> large for 'long' type
> 
> 
> 

Re: Reviewer wanted for JSON protocol implementation (THRIFT-1401)

[Jake Farrell]

Jens
A test case for this within the library would be very helpful, can you please 
include one with Thrift-1401  

Thanks
-Jake



On Oct 27, 2011, at 2:15 PM, Jens Geyer wrote:

> Hello Thrift developers,
> 
> I am looking for a helpful hand that wants to review my JSON protocol patch 
> against at least one other programming language to verify the correctness of 
> the protocol implementation. I have a small test case implemented running on 
> a web server,  and I can put both the IDL and the JSON server onto my web 
> site.
> 
> I surely could also provide an implementation of the standard test case 
> Trift.Test.thrift if necessary (even if that would require a little 
> additional work on my side, I can do that).
> 
> If you need more information, help or support with this, just give me a 
> mail.
> 
> Many thanks in advance,
> JensG 
> 

Re: ready to vote for a release?

[Jake Farrell]

Roger
I have been trying to get ready for an rc over the past week and there are a 
couple of tickets I was waiting on before proceeding.  I can create the 
0.8.0-rc1 once we decide on the following

-Jake


Thrift-1330 & 1392: php namespaces (fix in progress) 
Thrift-1421: debian package broken due to erlang (easy fix, remove erlang until 
jsx is fixed)
Thrift-1401: delphi json (waiting on someone to +1)
Thrift-1267: node.js Exceptions (waiting on test cases)
Thrift-1277: node.js booleans as null (broke lint test)



On Nov 8, 2011, at 5:59 PM, Roger Meier wrote:

> Yes
> 
> -roger
> 

RE: Thrift Web Site

[Jake Farrell]

I'm taking a looking to the CMS right now to see what it has to offer, if we go 
down the road of a site generator I think looking at something like jekyll 
would be a good idea. Using a backend of simple markdown file and the addition 
of syntax highlighting via pygments and its current use for github pages it 
should be easy for people to use and add content to

-Jake

 

From: Joe Schaefer [joe_schae...@yahoo.com]
Sent: Wednesday, November 23, 2011 4:05 PM
To: dev@thrift.apache.org
Subject: Re: Thrift Web Site

I'll still throw in my 2 cents for you guys to use the CMS.
We don't currently support Forrest sites, but a guinea pig
willing to sort that out would be appreciated.

In any case I'll get you guys on svnpubsub if you decide to
still not use the ASF CMS.  It's important to infra to get
you off rsync at some point.



- Original Message -
> From: Bryan Duxbury 
> To: dev@thrift.apache.org
> Cc:
> Sent: Wednesday, November 23, 2011 5:02 PM
> Subject: Re: Thrift Web Site
>
> Sounds like a worthy effort to continue.
>
> On Wed, Nov 23, 2011 at 1:23 PM, Roger Meier
> wrote:
>
>>  Hi all
>>
>>  I played a bit around with Apache Forrest and it might be an option to use
>>  it for a new Thrift Web Site.
>>  The homegrown static page generator CMS we have today is difficult to
>>  handle, so we get not that much contributions on documentation.
>>  Apache Forrest provides good formats to manage content and export it into
>>  several formats.
>>
>>  Here's a first example http://people.apache.org/~roger/thrift/
>>
>>  What do you think?
>>  Should I proceed with this?
>>  Is this an option to get better documentation?
>>  Merge Wiki, White Paper, etc. into a Forrest based Web Site?
>>
>>  -roger
>>
>>
>

Re: Thrift Web Site

[Jake Farrell]

I took a quick look at Jekyll last night and was able to convert the existing 
site over to markdown and get it up and running pretty quickly. I think using 
something like Jekyll or Hyde with markdown content would be beneficial because 
it would simplify the process for adding new tutorials and other items. The CMS 
looks like it will be a good option for static pages that are not in flux, but 
with our tutorials and other content needing so much work keeping the site in 
source control and getting patches from the community will allow for us to 
quickly generate content. Forest is great, but the setup, configuration and 
xdoc format is a little more than we currently need. Keeping it simple so 
people can easily submit back new pages will help get our site to where is 
should be. Here is the jekyll sample I threw together if anyone would like to 
take a look, css needs some cleaning up but overall concept is there

- Jake

Site:   http://people.apache.org/~jfarrell/
Source: http://people.apache.org/~jfarrell/jekyll/





On Nov 23, 2011, at 8:31 PM, Jake Farrell wrote:

> I'm taking a looking to the CMS right now to see what it has to offer, if we 
> go down the road of a site generator I think looking at something like jekyll 
> would be a good idea. Using a backend of simple markdown file and the 
> addition of syntax highlighting via pygments and its current use for github 
> pages it should be easy for people to use and add content to
> 
> -Jake
> 
> 
> 
> From: Joe Schaefer [joe_schae...@yahoo.com]
> Sent: Wednesday, November 23, 2011 4:05 PM
> To: dev@thrift.apache.org
> Subject: Re: Thrift Web Site
> 
> I'll still throw in my 2 cents for you guys to use the CMS.
> We don't currently support Forrest sites, but a guinea pig
> willing to sort that out would be appreciated.
> 
> In any case I'll get you guys on svnpubsub if you decide to
> still not use the ASF CMS.  It's important to infra to get
> you off rsync at some point.
> 
> 
> 
> - Original Message -
>> From: Bryan Duxbury 
>> To: dev@thrift.apache.org
>> Cc:
>> Sent: Wednesday, November 23, 2011 5:02 PM
>> Subject: Re: Thrift Web Site
>> 
>> Sounds like a worthy effort to continue.
>> 
>> On Wed, Nov 23, 2011 at 1:23 PM, Roger Meier
>> wrote:
>> 
>>> Hi all
>>> 
>>> I played a bit around with Apache Forrest and it might be an option to use
>>> it for a new Thrift Web Site.
>>> The homegrown static page generator CMS we have today is difficult to
>>> handle, so we get not that much contributions on documentation.
>>> Apache Forrest provides good formats to manage content and export it into
>>> several formats.
>>> 
>>> Here's a first example http://people.apache.org/~roger/thrift/
>>> 
>>> What do you think?
>>> Should I proceed with this?
>>> Is this an option to get better documentation?
>>> Merge Wiki, White Paper, etc. into a Forrest based Web Site?
>>> 
>>> -roger
>>> 
>>> 
>> 

[VOTE] Release Apache Thrift 0.8.0

[Jake Farrell]

All,
I propose that we accept 
http://people.apache.org/~jfarrell/thrift/0.8.0/thrift-0.8.0-rc0.tar.gz
as the official Thrift 0.8.0 release.

The release candidate is created from 
http://svn.apache.org/repos/asf/thrift/branches/0.8.x

The GPG signature can be found at: 
http://people.apache.org/~jfarrell/thrift/0.8.0/thrift-0.8.0-rc0.tar.gz.asc
It has an MD5 sum of 8703c67ef023d45d85c3228078f9b453

The CHANGES list for this release if available at:
http://svn.apache.org/repos/asf/thrift/branches/0.8.x/CHANGES

The Java artifacts for libthrift, libthrift-as3 and libfb303 are staged at:
https://repository.apache.org/content/repositories/orgapachethrift-255/

The debian packages, windows compiler, and packaged clients are available at:
http://people.apache.org/~jfarrell/thrift/0.8.0/

Please download, verify sig/sum, and install/test the libraries of your choice.

This vote closes in 72 hours.

-Jake

Thrift debain/ubuntu packages

[Jake Farrell]

I have been looking into trying to get the thrift compiler and libs into 
debian/ubuntu packages to help make it easier for people to install and start 
using thrift. Eric Evans, a Cassandra committer, has all ready started this as 
a sub project contained within github. He syncs with our code base and then 
runs scripts against it to create separate packages for the compiler, python 
and java to package. I've asked Eric to not submit his intent to package to 
debian so that we can come up with one unified way to handle all the packaging 
and add this into our release process moving forward. We will also need to find 
a debian mentor or sponsor until we can publish these artifacts on our own. 

Thoughts?

-Jake

Re: [VOTE] Release Apache Thrift 0.8.0

[Jake Farrell]

The gem can be built on ruby 1.9.2, it must have mongrel --pre installed in 
order for it to work. Since this is a specific issue to ruby 1.9.2 and not  any 
other version it does not make sense for force a specific pre version in the 
gemspec. 

-Jake


On Nov 29, 2011, at 5:03 PM, Ilya Maykov wrote:

> +1
> 
> Tested ruby 1.8.7 and 1.9.2 on Mac OS X. Tested Java on Mac OS X.
> 
> One minor issue: mongrel-1.1.5 is known to be broken with ruby 1.9.2, which
> is the version specified in lib/rb/Gemfile. That means you can't build the
> Ruby gem under 1.9.2. But this shouldn't matter, as the gem can be built
> with ruby 1.8.7 and still work in all common ruby versions.
> 
> -- Ilya
> 
> 
> On Sat, Nov 26, 2011 at 3:10 PM, Jake Farrell  wrote:
> 
>> All,
>> I propose that we accept
>> http://people.apache.org/~jfarrell/thrift/0.8.0/thrift-0.8.0-rc0.tar.gz
>> as the official Thrift 0.8.0 release.
>> 
>> The release candidate is created from
>> http://svn.apache.org/repos/asf/thrift/branches/0.8.x
>> 
>> The GPG signature can be found at:
>> http://people.apache.org/~jfarrell/thrift/0.8.0/thrift-0.8.0-rc0.tar.gz.asc
>> It has an MD5 sum of 8703c67ef023d45d85c3228078f9b453
>> 
>> The CHANGES list for this release if available at:
>> http://svn.apache.org/repos/asf/thrift/branches/0.8.x/CHANGES
>> 
>> The Java artifacts for libthrift, libthrift-as3 and libfb303 are staged at:
>> https://repository.apache.org/content/repositories/orgapachethrift-255/
>> 
>> The debian packages, windows compiler, and packaged clients are available
>> at:
>> http://people.apache.org/~jfarrell/thrift/0.8.0/
>> 
>> Please download, verify sig/sum, and install/test the libraries of your
>> choice.
>> 
>> This vote closes in 72 hours.
>> 
>> -Jake

Re: [jira] [Commented] (THRIFT-509) C# Library Does Not Provide Strong Name

[Jake Farrell]

If you would like to contribute back the spec files you have created and 
potentially move the generation and distribution of rpm's as part of our 
release process please create a ticket for this in jira, see 
http://wiki.apache.org/thrift/HowToContribute. We have been discussing 
packaging and distribution within the mailing list for deb packages and our 
goal is to work towards this for the 0.9 release. We would ideally like to 
control the process of submitting or publishing the packages to 
ubuntu/centos/fedora/etc either directly or through a mentor until we can take 
control of the entire process. 

-Jake




On Dec 12, 2011, at 11:09 AM, Nelson Marques (Commented) (JIRA) wrote:

> 
>[ 
> https://issues.apache.org/jira/browse/THRIFT-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167600#comment-13167600
>  ] 
> 
> Nelson Marques commented on THRIFT-509:
> ---
> 
> Hi,
> 
> I've recently packaged Thrift for EPEL (as my employer prefers we maintain 
> the packaging on a 'upstream' project than maintain them internally). When I 
> submitted the package to Fedora EPEL, I was asked to maintain it for Fedora 
> as well.
> 
> Now, for my needs I only need the cpp and php modules (which are the only 
> ones I provide on the EPEL version), unfortunatly for Fedora I was asked to 
> build all the modules that Fedora offers dependencies to. Most of it is done, 
> except for this tiny issue around the strong name.
> 
> Is there a way we can have a fix by upstream regarding this? I don't care how 
> much foolish it might be (including the swinging around with private keys), 
> but I really need to get this stuff done. Anyway we can have fix for 0.8.1 or 
> even a cherry picked patch from git is most likely welcome. I don't mind 
> maintaining the patch on Fedora if I have to and if you guys decide not 
> include it, but either way, I really could use a 'upstream approved' patch.
> 
> NM
> 
>> C# Library Does Not Provide Strong Name
>> ---
>> 
>>Key: THRIFT-509
>>URL: https://issues.apache.org/jira/browse/THRIFT-509
>>Project: Thrift
>> Issue Type: Bug
>> Components: C# - Library
>>Environment: Fedora 10 i386 - Mono version 2.0.1 - Thrift r770888
>>   Reporter: Silas Sewell
>>   Priority: Minor
>>Attachments: 
>> 0001-THRIFT-509.-Add-strong-name-signing-and-GAC-installa-v2.patch, 
>> 0001-THRIFT-509.-Add-strong-name-signing-and-GAC-installa.patch
>> 
>> 
>> I'm in the process of having a Thrift package reviewed for Fedora. 
>> Unfortunately the C# library is failing to register because it thinks 
>> Thrift.dll doesn't provide a "strong name".
>> If this is something that could be added to the library it would be very 
>> much appreciated.
>> Error:
>> DEBUG: + gacutil -i lib/csharp/Thrift.dll -f -package Thrift -root 
>> /builddir/build/BUILDROOT/thrift-0.0-0.fc10.20090501svn770888.i386/usr/lib
>> DEBUG: Failure adding assembly lib/csharp/Thrift.dll to the cache: Attempt 
>> to install an assembly without a strong name
>> Package Review: https://bugzilla.redhat.com/show_bug.cgi?id=498873
>> P.S. If I'm being stupid and this is something which I need to address in 
>> the build process please let me know.
> 
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA 
> administrators: 
> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
> 
> 

Decouple Thrift IDL from generators (THRIFT-1463)

[Jake Farrell]

Diwaker 
What is the issue you are trying to address that you are seeing in your day to 
day development with this ticket? Initially you could remove given languages 
not in use from the compiler and this was removed in favor of always having 
available every language that is possibly to be generated. This should have no 
impact on any test cases or libraries you wish to not include. Configure also 
offers the ability to compile without any of the client libs with the 
--without- option. This should allow you to compile and test the client 
libs that you are looking at using and you will not have to worry about 
dependencies for libraries you are not going to use. What problem are you 
running into that you are trying to address?

- Jake




On Dec 12, 2011, at 6:39 PM, Diwaker Gupta (Created) (JIRA) wrote:

> Decouple Thrift IDL from generators
> ---
> 
> Key: THRIFT-1463
> URL: https://issues.apache.org/jira/browse/THRIFT-1463
> Project: Thrift
>  Issue Type: Wish
>  Components: Compiler (General)
>Reporter: Diwaker Gupta
>Assignee: Jake Farrell
> 
> 
> While Thrift's broad language support is fantastic, it does impose many 
> constraints on day to day development.
> 
> * The current design of the compiler make it hard to improve and test the 
> generator/library for a particular language. The codebase is monolithic and 
> hard to navigate.
> * Each language has it's own idiosyncrasies. For instance, the Java library 
> required ant to build, the Ruby library has other dependencies. Running unit 
> tests is slightly different for each language library. Currently, all of this 
> is duck-taped together (barely) using 'make', which has its own flaws.
> * Adding support for a new language is fairly easy, but rather than making 
> the code more modular, it adds to the current complexity of the codebase. For 
> example, setting up Jenkins jobs to test/verify builds for a new language 
> take a while to come up to parity with other languages.
> 
> I think Google's Protocol Buffer approach is instructive here. They're trying 
> to strip down the core compiler and decouple the IDL from language specific 
> stubs. For a rich environment like Thrift, I think this decoupling is crucial 
> to allow for a more maintainable and testable code base going forward. To 
> refresh:
> 
> * the core compiler takes in a Thrift grammar file and generates an 
> intermediate representation: think of an in-memory AST
> * each supported language will be implemented via plugins, that can be loaded 
> at runtime by the compiler
> * the plugins take this AST and transform it into source code
> * each plugin can be in its own repository (consuming the compiler via a git 
> submodule, for instance). Plugins can freely choose their own build system, 
> unit test frameworks etc
> * a meta repository can contain the compiler, and the 'blessed' (officially 
> supported) languages. This meta repository can include integration tests that 
> will test language interoperability
> 
> I realize, of course, that this will be a big change. But we have to start 
> somewhere.
> 
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA 
> administrators: 
> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
> 
> 

Re: RFC patch: Java isset space optimization

[Jake Farrell]

Brian
if you would like to submit a patch for inclusion please see 
http://wiki.apache.org/thrift/HowToContribute

- Jake


On Dec 16, 2011, at 6:47 PM, Brian Bloniarz wrote:

> Hi, I have a small patch for Java to optimize the heapspace footprint
> of (for example):
> 
> struct OptIntPair {
>1: i32 a
>2: i32 b
> }
> 
> Each instance will have an __isset_bit_vector which points to a BitSet,
> which points to a long[], adding around 50 bytes of overhead to this object.
> 
> The patch changes this by storing a raw byte and doing direct bitfield 
> operations, like:
>  byte __isset_bitfield;
> 
>  public void unsetB() {
>__isset_bitfield = EncodingUtils.clearBit(__isset_bitfield, __B_ISSET_ID);
>  }
> A little nasty, but a big space win: on my machine, this brings down the total
> size of an OptIntPair from 85 bytes to 25 bytes. A BitSet gets used as a 
> fallback
> when more than 64 __isset entries are needed.
> 
> Is this something that could be considered? The patch is attached. Other 
> people have
> mentioned this shortcoming before, see slide 22 of:
> http://www.slideshare.net/aszegedi/everything-i-ever-learned-about-jvm-performance-tuning-twitter
> 
> Thanks for such useful software,
> Brian Bloniarz
> 

Re: Building on Mac OSX Lion?

[Jake Farrell]

I am running on lion with no issues. I compiled all dependencies by hand and 
did not use fink or ports for anything.  If you need compile lines I used for 
everything let me know and i can post them for you

-Jake


On Jan 1, 2012, at 1:37 PM, Anthony Molinaro wrote:

> Hi,
> 
>  I recently rebuilt my computer and was trying to get a dev environment
> up and running again under Lion.  I've been trying to get the dependencies
> via fink (for instance autoconf/automake/boost/pkg-config), but am running
> into compilation problems with HEAD.
> 
> Here's the current error
> 
> In file included from src/concurrency/ThreadManager.h:26,
> from src/concurrency/ThreadManager.cpp:24:
> src/concurrency/Thread.h: In static member function 'static uint64_t 
> apache::thrift::concurrency::Thread::get_current()':
> src/concurrency/Thread.h:91: error: invalid conversion from 
> '_opaque_pthread_t*' to 'uint64_t'
> 
> I tried hacking this with a cast, but that caused some other issue.
> 
> Does anyone have thrift building from HEAD under Lion, and if so can you
> share how you got your dependencies?
> 
> Thanks,
> 
> -Anthony
> 
> -- 
> 
> Anthony Molinaro   

Welcome Roger Meier to the Thrift PMC

[Jake Farrell]

I'm happy to announce Roger Meier as the latest addition to the Apache 
Thrift  Project Management Committee (PMC).

Roger has been an important committer to the project and member of 
the community. Congratulations Roger!

-Jake

Re: Versioning of erlang

[Jake Farrell]

Anthony
i'm good with that if it makes distributing the lib easier, just let me know 
where the version number needs to be updated so I can update it when making a 
release. Is there a standard place for erlang packages to be distributed from 
that I can go apply at so I could push the erl client package out with each 
release?

-Jake


On Feb 22, 2012, at 11:18 AM, Dmitriy Kargapolov wrote:

> On 02/22/2012 12:04 PM, Anthony Molinaro wrote:
>> On Wed, Feb 22, 2012 at 07:55:05AM -0500, Dmitriy Kargapolov wrote:
>>> On 02/22/2012 02:31 AM, Anthony Molinaro wrote:
 Hi,
 
  So I was noticing that many of the other bindings have the thrift
 version embedded in their libraries.  Turns out this would help with
 the usability of the erlang library as well, does anyone have an
 issue with me changing things to work in this way?
 
 Basically, I'd get rid of lib/src/thrift.app.src.in, and instead
 have a lib/src/thrift.app.src which has the version number in it.
 
 This file would need to be updated anytime the version is changed.
 
 Sound okay?
 
 -Anthony
 
>>> Once you run ./configure the correct version should be written instead
>>> of "@PACKAGE_VERSION@" macro in the resulting lib/erl/src/thrift.app.src
>>> anyway. What is the problem with this traditional approach?
>> Yes, I know I set it up that way, however, that doesn't play well with
>> rebar dependency management which is how most people want to build
>> their erlang these days.  In that case they'd like to do something like
>> 
>> {deps, [ { thrift, "0.9.0", {svn,
>>  "https://svn.apache.org/repos/asf/thrift/trunk/lib/erl/";, []}}]}.
>> 
>> in their rebar.config and have it work, the only thing preventing this
>> now is the fact that I took the route of substituting @PACKAGE_VERSION@.
>> 
>> However, looking through many of the other bindings I seem to be the
>> only one who took that approach, and its lead to many in the erlang
>> community forking off just the lib/erl directory which seems bad IMHO.
>> 
>> Since the other bindings seem to hardcode a version, it looks like
>> Jake updates them with releases, and if the erlang binding had a
>> hardcoded version it would allow people to build it independendently
>> via a rebar deps inclusion, I feel it would be the best course of
>> action to hardcode the version for the erlang library as well.
>> 
>> -Anthony
>> 
> Anthony,
> Thank you for detailed explanation. I would not follow community in what
> is not perfect per my opinion, but I understand your position. Actually,
> there are some much more important things to work on, performance is the
> fist one.
> Thanks again.

Re: [jira] [Commented] (THRIFT-1389) c_glib_generator.cc generates leaking code for cassandra_client_get_slice() and cassandra_client_get()

[Jake Farrell]

The ticket does not contain a fix version or patch with asf inclusion so
when looking for available tickets for a resease this would have been
missed unless someone was active on the ticket or searching for this
specific problem.

-Jake


http://thrift.apache.org/docs/HowToContribute/







On Thursday, March 29, 2012, Jerry Gally (Commented) (JIRA) wrote:

>
>[
> https://issues.apache.org/jira/browse/THRIFT-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241828#comment-13241828]
>
> Jerry Gally commented on THRIFT-1389:
> -
>
> When I ran accross this issue last year, and went searching for kindred
> spirits, I was left with the distinct impression that the C Thrift
> community was, as far as I could tell, virtually non-existent beyond the
> original _c_glib_generator.cc developer/contributer.
>
> Recieving your follow-up question on this issue is kind of like detecting
> a radio signal in the Search for Extra-Terrestrial Intellgence (SETI)
> program ;-)
>
> I, on the other hand, am no longer delving into the C Thrift context, but
> I do hope you find kindred spirits 8-)
>
> > c_glib_generator.cc generates leaking code for
> cassandra_client_get_slice() and cassandra_client_get()
> >
> --
> >
> > Key: THRIFT-1389
> > URL: https://issues.apache.org/jira/browse/THRIFT-1389
> > Project: Thrift
> >  Issue Type: Bug
> >  Components: C glib - Compiler, C glib - Library
> >Affects Versions: 0.6.1
> > Environment: Used with Cassandra 0.8.4 on Linux 2.6.32 with
> x86_64
> >Reporter: Jerry Gally
> >
> > The generated cassandra.c cassandra_client_recv_get_slice() code for
> list processing instantiates an object of TYPE_COLUMN_OR_SUPER_COLUMN  then
> calls thrift_struct_read() as in the following code snippet,:
> > <... snip>
> >   switch (fid)
> >   {
> > case 0:
> >   if (ftype == T_LIST)
> >   {
> > {
> >   guint32 size;
> >   ThriftType element_type;
> >   if ((ret = thrift_protocol_read_list_begin (protocol,
> &element_type, &size, error)) < 0)
> > return 0;
> >   xfer += ret;
> >   /* iterate through list elements */
> >   guint32 i;
> >   for (i = 0; i < size; i++)
> >   {
> > ColumnOrSuperColumn * _elem19;
> > _elem19 = g_object_new (TYPE_COLUMN_OR_SUPER_COLUMN,
> NULL);
> > //printf("\nrecv_slice made %p\n", _elem19->column);
> > if ((ret = thrift_struct_read (THRIFT_STRUCT (_elem19),
> protocol, error)) < 0)
> > <\snip ...>
> > When the object of TYPE_COLUMN_OR_SUPER_COLUMN is instantiated, it
> in-turn instantiates a child of TYPE_COLUMN:
> > <... snip>
> > void
> > column_or_super_column_instance_init (ColumnOrSuperColumn * object)
> > {
> >   /* satisfy -Wall */
> >   THRIFT_UNUSED_VAR (object);
> >   object->column = g_object_new (TYPE_COLUMN, NULL);
> >   object->__isset_column = FALSE;
> > 
> > But this instance reference is lost and replaced by a new TYPE_COLUMN
> instantiation reference when the column member is read by
> column_or_super_column_read() within the same execution context of the top
> level cassandra_client_recv_get_slice() call:
> > <... snip>
> > switch (fid)
> > {
> >   case 1:
> > if (ftype == T_STRUCT)
> > {
> >   this_object->column = g_object_new (TYPE_COLUMN, NULL);
> >   if ((ret = thrift_struct_read (THRIFT_STRUCT
> (this_object->column), protocol, error)) < 0)
> > 
> > The above snippits/logic/leak described above for
> cassandra_client_get_slice() also apply for cassandra_client_get().
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators:
> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>

[REPORT] Apache Thrift

[Jake Farrell]

July 2012

Thrift is a framework for providing cross-platform RPC and serialization.

Community
The Thrift community continues to see consistent growth with submissions
from
new contributors for bug fixes and new feature requests.

I am also happy to announce the addition of a new committer to the Apache
Thrift project, Henrique Mendonca.

Releases
We are finalizing preparation for our 0.9rc and are planning for the release
later this month.

Website
Updates to documentation and examples are in progress to go out with our 0.9
release. We will also be finalizing the svnpubsub switch over for the
website
this month (INFRA-5031 and INFRA-5032).

Re: Allowing annotations on Enum

[Jake Farrell]

We always welcome new functionality and patches, please see
http://thrift.apache.org/docs/HowToContribute/ for how to submit a patch

-Jake



On Tue, Jul 10, 2012 at 7:00 PM, Benjy Weinberger  wrote:

> Thrift currently allows annotations on all elements other than enum
> and senum (and their values). Is this by design, or is it oversight?
> If the latter, any objection to me submitting a patch to allow those
> annotations?
>
> Thanks!
>
> Benjy
>

[Announcement] New Committer Henrique Mendonca

[Jake Farrell]

On behalf of the Apache Thrift PMC, I would like to welcome a new committer
to
the project:

  Henrique Mendonca

He has sustained high quality contributions to the project and it is my
honor
to welcome him as a committer.

Congratulations, and thanks for your hard work so far.

Jake Farrell
Apache Thrift PMC

Re: Thrift 0.9.0 release date?

[Jake Farrell]

I have been sorting through tickets and getting ready to make the 0.9.0 rc
shortly

-Jake


On Tue, Sep 4, 2012 at 9:24 PM, Diwaker Gupta wrote:

> Folks,
>
> Is there a date for Thrift 0.9.0 release? Per JIRA, there are only 4
> unresolved issues targeted for 0.9.0. There have been tons of bug
> fixes and enhancements (notably for building on Windows) since 0.8.0
> that I'd like to uptake.
>
> cheers,
> Diwaker
> --
> http://maginatics.com
>

[Report] Apache Thrift

[Jake Farrell]

September 2012

Thrift is a framework for providing cross-platform RPC and serialization.

Community
The Thrift community continues to see consistent growth with submissions
from
new contributors for bug fixes and new feature requests.

Releases
Our 0.9 release was delayed to some major issues found during testing last
month which would affected other Apache projects leveraging Thrift. We
have worked through these issues as well as added functionality and
upgraded
our client libraries during this time. The 0.9 release candidate will be
available
this month and we will be working with infra to test on the new ARM cluster.

Website
Svnpubsub switch is now complete for Thrift and worked through an issue with
pypi easy_install client for python having trouble with dist.a.o due to
url length.
Tutorials and content on the website has seen an increase in community
additions since switching to markdown and we are continuing to migrate
Thrift
documentation and tutorials to the main site.


-Jake

Re: JIRA attachments

[Jake Farrell]

It was removed during the jira upgrade, the patch upload implies that it
has been granted for ASF use now

-Jake



On Tuesday, September 11, 2012, Jens Geyer wrote:

> Jake,
>
> is there no more an "[x] grant ASF license" checkbox when adding an
> attachment or do I just not see it?
>
> JensG
>
>
>

Re: Build thrift without warning

[Jake Farrell]

James, Ben
Please see http://thrift.apache.org/docs/HowToContribute/ for submitting
patches back to be included in Apache Thrift

Thanks
Jake




On Sat, Sep 15, 2012 at 9:45 PM, Ben Craig  wrote:

> I have a similar (all in one) patch that I can post on Monday.
>
> James,
> One thing I noticed in your patch was that you still cast the SOCKET type
> to int in several places.  This will appear to work most of the time on
> Win64, but the upper 32 bits are used in some situations.  Discarding the
> upper 32-bits will cause problems in those situations.
>
> The patch doesn't address the non-blocking server (which is fine, my patch
> won't either).  It also doesn't address some HANDLE->int casts in the
> PipeServer that show up when you enable Visual Studio's /WP64 warning flag
> (again, neither will mine).
>
>
> From:   "James K. Lowden" 
> To: dev@thrift.apache.org
> Date:   09/15/2012 03:02 PM
> Subject:Build thrift without warning
>
>
>
> http://www.schemamania.org/thrift/patch/
>
> The patches at the above URL allow the current trunk of Thrift C++ to
> build without warnings in Visual Studio and GNU gcc.
>
> I introduce THRIFT_SAFE_CAST in Thrift.h, which tests narrowing
> conversions for fit.  Would-be overflows throw std::runtime_error.
>
> Some functions have been modified or overloaded to allow size_t
> parameters.  SOCKET is dealt with intelligently.
>
> IMO every public thrift function should have a form accepting normal
> types -- including e.g. short, int, long, and size_t -- and apply casts
> as necessary.  In particular size_t is important because std
> constainers have size() members that usually return something like
> size_t.
>
> Enjoy!
>
> --jkl
>
>

Re: Build thrift without warning

[Jake Farrell]

James
As David explained the how to contribute page on our website is an ASF
requirement legally due to any contributions being part of the collective
work and protected by copyright law and owned by the ASF.

I appreciate the work that you have done here and that you have brought it
back to the community, contributions like this are what helps make Apache
Thrift great software. My original message was solely to make sure that
Apache Thrift complies with all regulations as set forth by the ASF. I
agree that the how to contribute page should have some explanation as to
why a patch is required, and I will add something to the website for this.

Thank you for creating THRIFT-1695 and including your work there

-Jake




On Sun, Sep 16, 2012 at 1:35 PM, James K. Lowden
wrote:

> On Sun, 16 Sep 2012 09:51:01 -0700
> David Reiss  wrote:
>
> > The submission process isn't just a formality.  It's necessary to
> > protect the foundation legally.  If the maintainers were allowed to
> > import patches from the Internet just based on an email and a URL,
> > there would be too much risk that a third party could claim to own
> > the code and sue the Apache Foundation.
>
> David, thanks for the explanation.  OK, will do.  Could I suggest that
> something to that effect be included in HowToContribute?
>
> > I'm sorry for the inconvenience.
>
> It's too bad it's come to this.  Apache itself was created without any
> such framework.  For many years I was unable to contribute to GNU
> because they demanded a release even though my employer claimed no
> rights to my work.
>
> Regards,
>
> --jkl
>

Re: [PATCH] base class for struct in c++?

[Jake Farrell]

Martin
Thank you for bringing this to the community, please see
http://thrift.apache.org/docs/HowToContribute/ for instructions on
contribution back patches like this.

-Jake


On Fri, Sep 28, 2012 at 12:53 PM, Martin Vogt  wrote:

> Hello,
>
> I would like to use the c++ generator for structs
> in a QT application with signal/slots.
>
> For example:
>
> thrift:
> struct Matrix
> {
>   1: required i64 rows=123,
>   2:i64 cols,
>   3:list data,
> }
>
> QT class:
> emit(mySignal(TBase*))
>
> where TBase is a common base class for the generated
> struct/class Matrix.
>
> Then some receiver can check if the class which
> they receive like this:
>
> QT Slot:
> void myMatrixSlot(TBase* tBase) [
>  if (tBase->compare(Matrix::ascii_fingerprint)==0) {
>Matrix* matrix=(Matrix*)tBase;
>// work with matrix
>//
>  }
> }
>
> The problem is that the current cpp generator does not generate
> such a base class. The attached patch is a first modification
> which I used for my tests.
>
> Is it possible to add such a baseclass extension into
> the thrift repository?
>
> regards,
>
> Martin
>

[Report] Apache Thrift

[Jake Farrell]

October 2012

Thrift is a framework for providing cross-platform RPC and serialization.

Community
The Thrift community continues to see consistent growth with new
contributors
enchaining Thrift and closing bugs at a steady rate. The upcoming release
shows this growth in having 50+ more tickets resolved than past releases.

Releases
With help from Gavin @infra the jenkins build slaves have been upgraded to
help Thrift utilize the newest versions of client library dependencies.

The 0.9 release candidate is in the process of being packaged for a vote
with
THRIFT-1721 as the only remaining blocker which has a patch available and is
currently getting tested (sub-ticket THRIFT-1722 breaks deb build which is
needed for INFRA-4081).

Website
Community contributions for documentation and updates to the website are
coming in and the tutorials section of the site is starting to take shape
with new
content and examples.


-Jake

[VOTE] Release Apache Thrift 0.9.0

[Jake Farrell]

All,
I propose that we accept
http://people.apache.org/~jfarrell/thrift/0.9.0/thrift-0.9.0-rc.tar.gz
as the official Thrift 0.9.0 release.

The release candidate is created from
http://svn.apache.org/repos/asf/thrift/branches/0.9.x

The GPG signature can be found at:
http://people.apache.org/~jfarrell/thrift/0.9.0/thrift-0.9.0-rc.tar.gz.asc
It has an MD5 sum of a42c37b645a9103192ad7dfabe4f0086

The CHANGES list for this release if available at:
http://svn.apache.org/repos/asf/thrift/branches/0.9.x/CHANGES

The Java artifacts for libthrift, libthrift-as3 and libfb303 are available
at:
http://people.apache.org/~jfarrell/thrift/0.9.0/lib/java
http://people.apache.org/~jfarrell/thrift/0.9.0/lib/as3
http://people.apache.org/~jfarrell/thrift/0.9.0/contrib/fb303/java

The debian packages, windows compiler, and packaged clients are
available at:
http://people.apache.org/~jfarrell/thrift/0.9.0/

Please download, verify sig/sum, and install/test the libraries of your
choice.

This vote closes in 72 hours.

-Jake

Re: [VOTE] Release Apache Thrift 0.9.0

[Jake Farrell]

With 3 binding +1's, 1 other +1 and no -1's the 0.9.0 release candidate
passes. I'll get it ready and start distributing the release shortly.

Thanks to all who contributed to this release
-Jake



On Thu, Oct 11, 2012 at 9:15 PM, Jake Farrell  wrote:

> All,
> I propose that we accept
> http://people.apache.org/~jfarrell/thrift/0.9.0/thrift-0.9.0-rc.tar.gz
> as the official Thrift 0.9.0 release.
>
> The release candidate is created from
> http://svn.apache.org/repos/asf/thrift/branches/0.9.x
>
> The GPG signature can be found at:
> http://people.apache.org/~jfarrell/thrift/0.9.0/thrift-0.9.0-rc.tar.gz.asc
> It has an MD5 sum of a42c37b645a9103192ad7dfabe4f0086
>
> The CHANGES list for this release if available at:
> http://svn.apache.org/repos/asf/thrift/branches/0.9.x/CHANGES
>
> The Java artifacts for libthrift, libthrift-as3 and libfb303 are available
> at:
> http://people.apache.org/~jfarrell/thrift/0.9.0/lib/java
> http://people.apache.org/~jfarrell/thrift/0.9.0/lib/as3
> http://people.apache.org/~jfarrell/thrift/0.9.0/contrib/fb303/java
>
> The debian packages, windows compiler, and packaged clients are
> available at:
> http://people.apache.org/~jfarrell/thrift/0.9.0/
>
> Please download, verify sig/sum, and install/test the libraries of your
> choice.
>
> This vote closes in 72 hours.
>
> -Jake
>

[Announcement] New Committer: Jens Geyer

[Jake Farrell]

On behalf of the Apache Thrift PMC, I would like to welcome a new committer
to
the project:

  Jens Geyer

He has sustained high quality contributions to the project and it is my
honor
to welcome him as a committer.

Congratulations, and thanks for your hard work so far.

Jake Farrell
Apache Thrift PMC

Apache Thrift git migration

[Jake Farrell]

We have started the process of migrating our svn repository over to git. We
are switching the svn repository to read only so please refrain from making
any commits to svn. I will send out another email when the process is
finished and what the new git repository information is.

Thanks
-Jake

Re: AW: Apache Thrift git migration

[Jake Farrell]

All repos are still read 
only, I have followed up with infra and will continue to watch the 
process and let everyone know when the switch is finalized 

-Jake


   	   
   	Roger Meier  
  December 7, 2012 
4:40 PM
  Any news?

Should I try git here https://git-wip-us.apache.org/repos/asf/thrift.git

-roger

-Ursprüngliche Nachricht-
Von: Jake Farrell [mailto:jfarr...@apache.org]
Gesendet: Mittwoch, 28. November 2012 17:51
An: dev@thrift.apache.org
Betreff: Apache Thrift git migration

We have started the process of migrating our svn repository over to git.
We
are switching the svn repository to read only so please refrain from
making
any commits to svn. I will send out another email when the process is
finished and what the new git repository information is.

Thanks
-Jake


   	   
   	Jake Farrell  
  November 28, 2012
 11:50 AM
  We have started the 
process of migrating our svn repository over to git. We are switching 
the svn repository to read only so please refrain from making any 
commits to svn. I will send out another email when the process is 
finished and what the new git repository information is.
Thanks-Jake

  

Re: AW: Apache Thrift git migration

[Jake Farrell]

The Apache Thrift 
repo is now converted over to git. I will get the 
website updated later tonight with all the new details. If anyone has 
any issues or questions please let me know

-Jake

Committers: https://git-wip-us.apache.org/repos/asf/thrift
Browse: https://git-wip-us.apache.org/repos/asf?p=thrift.git 



   	   
   	Jake Farrell  
  December 8, 2012 
11:42 AM
  

All repos are still read 
only, I have followed up with infra and will continue to watch the 
process and let everyone know when the switch is finalized 

-Jake


  
   	   
   	Roger Meier  
  December 7, 2012 
4:40 PM
  Any news?

Should I try git here https://git-wip-us.apache.org/repos/asf/thrift.git

-roger

-Ursprüngliche Nachricht-
Von: Jake Farrell [mailto:jfarr...@apache.org]
Gesendet: Mittwoch, 28. November 2012 17:51
An: dev@thrift.apache.org
Betreff: Apache Thrift git migration

We have started the process of migrating our svn repository over to git.
We
are switching the svn repository to read only so please refrain from
making
any commits to svn. I will send out another email when the process is
finished and what the new git repository information is.

Thanks
-Jake


   	   
   	Jake Farrell  
  November 28, 2012
 11:50 AM
  We have started the 
process of migrating our svn repository over to git. We are switching 
the svn repository to read only so please refrain from making any 
commits to svn. I will send out another email when the process is 
finished and what the new git repository information is.
Thanks-Jake

  

[Report] Apache Thrift

[Jake Farrell]

January 2013

Thrift is a framework for providing cross-platform RPC and serialization.

Community
The Thrift community continues to see consistent growth with an increase 
in new
contributors. Since our recent 0.9 release we have resolved almost 50 
tickets and

we are working towards our milestone 1.0 release.

Releases
Version 0.9.0 released.

General
The Apache Thrift PMC voted to switch from svn to git as our primary 
source control
management. The website and svn repo has been updated with the links to 
the new
repository and we are seeing an overwhelming positive response from the 
community

for this change.


-Jake

Re: Thrift Haskell Build Error

[Jake Farrell]

Hi Doug
If you could please create a ticket for this issue and also one for 
releasing the client lib to hackage I would be glad to add it to the 
release process


-Jake


MightyByte wrote:


Hi,

The Thrift library for Haskell has a build error with GHC 7.6. I fixed it
by removing the explicit import on line 30 of
src/Thrift/Transport/Handle.hs. Could you upload a new version to hackage?
Thanks.

Doug Beardsley

Re: [jira] [Commented] (THRIFT-1357) Erlang Dependency breaks build

[Jake Farrell]

This would be on the 
ubuntu build slaves which have all been upgraded to ubuntu 12.04 and 
have the following erlang packages installed

erlang-base
erlang-crypto
erlang-dev
erlang-eunit
erlang-syntax-tools


-Jake

  
 	   
  
   	Anthony Molinaro
  
  March 24, 2013 
7:21 PM
  
  What's the build 
environment?  Eunit is part of the erlang distro normally.-Anthony
   	   
   	Roger Meier (JIRA)  
  March 24, 2013 
5:55 PM
  [ 
https://issues.apache.org/jira/browse/THRIFT-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612266#comment-13612266
 ] Roger Meier commented on THRIFT-1357:-erlang
 guys where are you?unit tests still fail:{noformat}./rebar
 eunit==> jsx (eunit)src/jsx_verify.erl:89: can't find 
include lib "eunit/include/eunit.hrl"src/jsx_verify.erl:93: 
undefined macro '_assert/1'src/jsx_verify.erl:144: undefined macro 
'_assertNot/1'src/jsx_verify.erl:163: undefined macro 
'_assertMatch/2'src/jsx_verify.erl:168: undefined macro '_assert/1'src/jsx_verify.erl:202:
 undefined macro '_assertNot/1'make: *** [check] Error 1{noformat}
--This message is 
automatically generated by JIRA.If you think it was sent 
incorrectly, please contact your JIRA administratorsFor more 
information on JIRA, see: http://www.atlassian.com/software/jira

Re: Want to contribute to Apache Thrift

[Jake Farrell]

Hi Tushar
Glad to hear you are enjoying Apache Thrift and want to contribute back.
Please see http://thrift.apache.org/docs/HowToContribute/ for details on
submitting patches and if you have any questions you can email the dev
mailing list or ask in #thrift on freenode

-Jake



On Mon, Mar 25, 2013 at 8:23 AM, Tushar Sudake  wrote:

> Hi Dev Team,
>
> I have used (basic) of thrift recently. And found it very awesome and
> beautiful.
>
> I'm thinking of contributing to it, in any way..let it be documentation,
> wiki, source etc. This is the first time I'm contributing to open source
> community.
> Can someone please help me with this? What are some things that I must
> know. How can I add unit tests for the patches that I submit?..I mean
> fitting them into existing test framework. And most importantly,
> understanding the source code (even at high level).
>
> To begin, I'm planning to start with easy thing like THRIFT-1844 JIRA.
>
> Thanks in advance.
> Tushar
>

Re: [jira] [Closed] (THRIFT-984) ocaml: add version Info to the library

[Jake Farrell]

Chet
A tutorial would be great, thanks. you can submit a patch for the main 
repository as tutorial/ocaml or submit a patch to the websites tutorials
 section http://svn.apache.org/repos/asf/thrift/site/

-Jake


   	   
   	Chet Murthy  
  March 26, 2013 
2:47 PM
  [Oops, replied to the 
wrong email from you]Jake, I also have ocaml versions of the 
tutorial programs that I couldcreate a JIRA item for and upload, if 
that'd be of any use.  --chet--

Re: [jira] [Closed] (THRIFT-984) ocaml: add version Info to the library

[Jake Farrell]

Hey Chet
The steps detailed at http://thrift.apache.org/docs/HowToContribute/ are
 for submitting patches for new additions, bugfixes and any code for the
 website and code base, like the tutorial you uploaded to THRIFT-1906. 
I'll outline the necessary steps below and hopefully explain them a 
little better detail and if you have any questions please let me know. 

Thank you for contributing, the help is greatly appreciated
-Jake


1. Look in jira (https://issues.apache.org/jira/browse/THRIFT) to make 
sure there is not a ticket all ready open for the issue you are 
experiencing, or if it is a new feature that there is a ticket open with
 work in progress. If there is not then create a new ticket (THRIFT-1906
 in your case for a ocaml tutorial, perfect)

2. Checkout our code base to start working on it for the ticket created 
in step 1.
    
        git clone https://git-wip-us.apache.org/repos/asf/thrift.git 
thrift

3. Modify the source code for the new feature or bug fix you are working
 on as described in the ticket in step 1.

4. Create a patch for the additions or changes you have made and attach 
the patch to the ticket in step 1. This step is necessary because by 
uploading the patch to issues.apache.org you are granting use to the ASF
 for the code you have written.  

        git diff > ../thrift-XXX-my-new-feature.patch

5. A committer will review your patch attached to the ticket and commit 
it on your behalf to the master repository and close the ticket for you.






   	   
   	Chet Murthy  
  March 27, 2013 
3:54 PM
  Jake,I am unclear 
on what you mean (and "HowToContribute" didn't reallyexplain it) so I(a)
 created a JIRA issue  
https://issues.apache.org/jira/browse/THRIFT-1906?page=com.atlassian.jirafisheyeplugin:fisheye-issuepanel(b)
 uploaded a tarball with the new files.If this isn't correct, 
and you could point me at whatever the rightwiki page is with 
instructions on how to do it, I'll be glad to do itproperly.Cheers,--chet--
   	   
   	Jake Farrell  
  March 26, 2013 
6:16 PM
  

Chet
A tutorial would be great, thanks. you can submit a patch for the main 
repository as tutorial/ocaml or submit a patch to the websites tutorials
 section http://svn.apache.org/repos/asf/thrift/site/

-Jake


  
   	   
   	Chet Murthy  
  March 26, 2013 
2:47 PM
  [Oops, replied to the 
wrong email from you]Jake, I also have ocaml versions of the 
tutorial programs that I couldcreate a JIRA item for and upload, if 
that'd be of any use.  --chet--

Re: Wiki Spam

[Jake Farrell]

Thanks Randy
We have been moving content to the website and off from the wiki due to
issues like spam and attachment problems. Ill go through and get the wiki
cleaned up from these links. Please have a look at
http://thrift.apache.org/docs/install/ and if you would like to contribute
to the site we accept patches attached to tickets in jira


-Jake




On Sunday, March 31, 2013, Randy Abernethy wrote:

> Hello all,
>
> Looking through the wiki and found this page spammed but did not know how
> to revert it:
> http://wiki.apache.org/thrift/ThriftRequirements
>
> also all of the links posted on the front page look bogus.
>
> Regards,
> Randy
>

[Report] Apache Thrift

[Jake Farrell]

April 2013

Thrift is a framework for providing cross-platform RPC and serialization.

Project Status
-
The Thrift community continues to see consistent growth with an increase 
in new

contributors. The adoption of git as our primary source repository has been
extremely well received, over the past 30 days there have been 43 new 
tickets

created and 42 tickets resolved.


Community
---
Bryan Duxbury has elected to step down as the Thrift PMC chair. The PMC has
voted a new chair and a resolution has been sent to the board.


Releases

Progress continues towards our 1.0 release with improvements to automated
testing, version upgrades, and bug fixes to the client libraries.


-Jake

Re: Update hackage

[Jake Farrell]

Thanks Alex for pointing this out, created THRIFT-1940 to address this

-Jake



On Mon, Apr 22, 2013 at 6:13 AM, Alex Good  wrote:

> Hey!
>
> Woud it be possible to update the hackage entry for thrift[1] with the
> latest version?
>
> Thanks
> Alex
>
> [1] 
> http://hackage.haskell.org/**package/thrift
>

Welcome Jens Geyer To Apache Thrift PMC

[Jake Farrell]

I'm happy to announce Jens Geyer as the latest addition to the Apache Thrift
Project Management Committee (PMC).

Jens has been an important committer to the project and active member of 
the

community helping advance Apache Thrift.

Congratulations, and thank you for your hard work

- Jake
Apache Thrift PMC

[Announcement] New Committer: Carl Yeksigian

[Jake Farrell]

On behalf of the Apache Thrift PMC, I would like to welcome our newest
committer to the project:

  Carl Yeksigian

He has been extremely active contributing quality patches and working to
advance the client libraries and it is my honor to welcome him as a 
committer.


Congratulations and thank you for your hard work
Jake Farrell
Apache Thrift PMC

Re: 1.0 release?

[Jake Farrell]

Hey Brock
We have 51 open issues with 10 critical and above tickets for the 1.0 
release. I would say we are about 1-2 months out on a release based on 
typical ticket resolution rates 

-Jake




   	   
   	Brock Noland  
  June 4, 2013 1:56
 PM
  When do we think the 1.0 
release will occur?I am interested inTHRIFT-1869
 forApache Hive :)Brock

Re: introduce --signoff ?

[Jake Farrell]

--signoff
 would be appropriate use in this case as the committer is 
directly involved with the delivery if the patch from the --author and 
the --author has granted use of that work to the ASF by attaching the 
patch to an issue within Jira at issues.apache.org.  

Since contributors do not necessarily have an ICLA's on file the 
committer is the one responsible for marking the work being committed as
 "Submitted on behalf of a third-party: [named here]", see Apache ICLA 
section 7. We currently comply with this with our commits having "Patch:
 [named here]". As I am unaware of any other project doing this and it 
is a change to how code is submitted back to the ASF we should bounce 
off board/legal to cover all bases if we go down the path of an official
 proposal and vote on this.
  
Finally, if we do consider switching the author and using signing to 
note the committer then I think we need to look at using gpg
 signatures as well to validate that the commit has truly come from a 
trusted committer. This will add a number of additional steps for new 
committers and existing ones who do not have a gpg key created and 
published, currently we only have 6. 
  
 
-Jake

References:
- http://www.apache.org/dev/committers.html#applying-patches
 
- http://www.apache.org/licenses/icla.pdf




   	   
   	Evan Nemerson  
  June 20, 2013 
7:16 PM
  I may be 
misunderstanding your intent here, but I believe this is stillsomewhat
 non-standard usage of Signed-off-by.  Typically it is used toindicate
 that someone either wrote it and/or have the right toopen-source 
the contribution.  See the Linux kernel's documentationhere: 
https://www.kernel.org/doc/Documentation/SubmittingPatches(section 
12).I think what you're really after is "Acked-by" (or possibly 
"Tested-by"or "Reviewed-by"), which is described in section 13 of 
that document.If all you want is to signify who actually committed 
the patch, thatinformation is already retained by git.  It doesn't 
show up in `git log`by default, but `git log --format=full` will 
show it, as will gitweb andcgit.As long as on the subject, 
most open source projects try to limit thesubject of the patch to 72
 characters (or another number in the 70-75range), and include the 
relevant component.  If a longer description isnecessary that goes 
in subsequent lines.  Finally, the bug informationcomes at the end. 
 So, that commit would look something like this:$ git commit 
--author "Cross Everything " --signoffNote
 the absence of -m.  Then, in your editor (nano, vi, emacs, etc...see
 the "ENVIRONMENT AND CONFIGURATION VARIABLES" section in thegit-commit
 man page for details) enter in the commit message, whichwould be 
something like:cpp: fix warning on 64-bit platforms 
about truncating rlim_t tointA 
longer description of the problem and/or solution could go
here if the subject is insufficient to convey everything.
THRIFT-2024Instead of "THRIFT-2024", many (most?) 
projects use an actual link tothe bug in question instead of just 
the bug number, which is quiteconvenient.-Evan
   	   
   	Roger Meier  
  June 20, 2013 
5:53 PM
  yes, you are right.

git commit --signoff --author="Cross Everything 
" -a -m "THRIFT- lang: description"

does the trick!

I've just tested it here including also signoff:
https://git-wip-us.apache.org/repos/asf?p=thrift.git;a=commit;h=cc25c52de4fc1d9d856a759b283ff96a6c251c29

https://issues.apache.org/jira/browse/THRIFT-2024


update here: http://thrift.apache.org/docs/HowToContribute ?

-roger


Quoting Carl Yeksigian :




   	   
   	Carl Yeksigian  
  June 19, 2013 
8:39 PM
  I think it might be better
 attribution to use --author="(author)", if thisis for attribution.That
 way the authorship can go to the person who authored the patch;committer
 will remain the committer's name. Just for a preview, I just madea 
test commit to a review branch on my github, so if interested in whatthat
 might look like:https://github.com/carlyeks/thrift/commit/2f96496856710c4bbff1890241b064561e0da2c6On
 Jun 20, 2013, at 12:44 AM, Roger Meier  
wrote:what about using the signoff feature for contributions?git
 commit --signoff -a -m "THRIFT- lang: description"roger;-r
   	   
   	Roger Meier  
  June 19, 2013 
6:43 PM
  what about using the signoff 
feature for contributions?
git commit --signoff -a -m "THRIFT- lang: description"

roger
;-r

Re: RPM for thrift?

[Jake Farrell]

Hi John
There is a spec file located in the contrib folder which you can use with
rpmbuild to create an rpm (I recently edited it so I know its current). I
can add that to the release process similar to the deb's currently generate
during the next rc testing. If you have any questions let me know

-Jake


On Fri, Jun 21, 2013 at 1:48 PM, John R. Frank  wrote:

>
> Thrifters -- does anyone have an RPM for thrift?  I'm seeing people
> re-compile it again and again on different machines...
>
> If there is not yet a community RPM, would the maintainers entertain a
> contribution?  If anyone would like to build an RPM well enough that it can
> become official and released through apache (big top maybe?), we might be
> able to help underwrite that.
>
> Perhaps someone can start with this:
>
> https://sites.google.com/a/**blamethecomputer.com/segfault/**
> braindump/building-and-**installing-thrift-on-centos-5
>
>
> jrf
>
>

Re: AS3: Fix for missing OPTIONAL support while serializing structs

[Jake Farrell]

Ravid
Thank you for looking into this issue and the patch. Can you please create
an issues in our ticketing system, jira, and attach the patch to a new
issue there. Details on this process are available at
http://thrift.apache.org/docs/HowToContribute/ . If you have any questions
please let us know

Appreciate the help
Thanks
-Jake




On Fri, Aug 16, 2013 at 7:01 AM, Ravid Rosen-Tal wrote:

> Hello,
>
> I've been using thrift for a while now to communicate between java backend
> and flash front-end. Recently I found an issue with the compiler with
> serialisation of structs with un-set optional fields. The generated 'write'
> method would not look at the __isset flag for optional fields, and instead
> would explicitly write all fields, causing issues in validation when
> structs are deserialized.
>
> The attached file is a suggest fix, inspired from the t_java_generator
> class.
>
> Please consider adding this fix to the next build.
>
> Thanks,
> Ravid
>
>
>
>

Apache Thrift Builds

[Jake Farrell]

We are back to having successful jenkins builds again for Apache Thrift!

Job details can be found at: https://builds.apache.org/job/Thrift/

-Jake

[VOTE] Release Apache Thrift 0.9.1

[Jake Farrell]

All,
I propose that we accept the following release candidate as the official
Apache Thrift 0.9.1 release.

http://people.apache.org/~jfarrell/thrift/0.9.1/thrift-0.9.1-rc.tar.gz


The release candidate is created from the 0.9.1 branch and can be cloned
using:
git clone -b 0.9.1 http://git-wip-us.apache.org/repos/asf/thrift.git

The release candidates GPG signature can be found at:
http://people.apache.org/~jfarrell/thrift/0.9.1/thrift-0.9.1-rc.tar.gz.asc
It has an MD5 sum of 8a8dd3e84bd59bfe33f7f07e931248a1

The CHANGES list for this release is available at:
https://git-wip-us.apache.org/repos/asf?p=thrift.git;a=tree;h=refs/heads/0.9.1;hb=0.9.1

Client libraries are available for testing at:
http://people.apache.org/~jfarrell/thrift/0.9.1/lib/

The deb packages are available at:
http://people.apache.org/~jfarrell/thrift/0.9.1/contrib/deb/

The windows compiler is available at:
http://people.apache.org/~jfarrell/thrift/0.9.1/windows/


Please download, verify sig/sum, and install/test the libraries of your
choice.

This vote will close in 72 hours.

-Jake

Re: [VOTE] Release Apache Thrift 0.9.1

[Jake Farrell]

Hey Ben

> [minor] The CHANGES files doesn't list a language for a lot of the 0.9.1
changes

if there is no component set in the ticket then this is blank.

> [minor] This is a larger 0.9.1 than I initially thought it was going to be.
 I vaguely recall that 0.9.1 was going to add multiplexing, and little else.
 Why the change?  Why 0.9.1 instead of 1.0?

We decided that with the number of closed tickets that a release was needed
(ended with 192 in the rc) and there are a couple of key features that we
would like to see make it in before we publish the milestone 1.0 release.

Thanks for testing and if you have any other questions happy to answer them

-Jake




On Mon, Aug 19, 2013 at 9:51 AM, Ben Craig  wrote:

> Ship it!
>
>
> [minor] The CHANGES files doesn't list a language for a lot of the 0.9.1
> changes
> [minor] This is a larger 0.9.1 than I initially thought it was going to
> be.  I vaguely recall that 0.9.1 was going to add multiplexing, and little
> else.  Why the change?  Why 0.9.1 instead of 1.0?
>
>
>
> From:   Jake Farrell 
> To: "dev@thrift.apache.org" ,
> Date:   08/18/2013 07:11 PM
> Subject:[VOTE] Release Apache Thrift 0.9.1
>
>
>
> All,
> I propose that we accept the following release candidate as the official
> Apache Thrift 0.9.1 release.
>
> http://people.apache.org/~jfarrell/thrift/0.9.1/thrift-0.9.1-rc.tar.gz
>
>
> The release candidate is created from the 0.9.1 branch and can be cloned
> using:
> git clone -b 0.9.1 http://git-wip-us.apache.org/repos/asf/thrift.git
>
> The release candidates GPG signature can be found at:
> http://people.apache.org/~jfarrell/thrift/0.9.1/thrift-0.9.1-rc.tar.gz.asc
> It has an MD5 sum of 8a8dd3e84bd59bfe33f7f07e931248a1
>
> The CHANGES list for this release is available at:
>
> https://git-wip-us.apache.org/repos/asf?p=thrift.git;a=tree;h=refs/heads/0.9.1;hb=0.9.1
>
>
> Client libraries are available for testing at:
> http://people.apache.org/~jfarrell/thrift/0.9.1/lib/
>
> The deb packages are available at:
> http://people.apache.org/~jfarrell/thrift/0.9.1/contrib/deb/
>
> The windows compiler is available at:
> http://people.apache.org/~jfarrell/thrift/0.9.1/windows/
>
>
> Please download, verify sig/sum, and install/test the libraries of your
> choice.
>
> This vote will close in 72 hours.
>
> -Jake
>
>

Re: [VOTE][RESULT] Release Apache Thrift 0.9.1

[Jake Farrell]

Including my own vote of +1 we have 4 binding +1, 2 other +1 and no -1. The
vote for the Apache Thrift 0.9.1 release passes. Thank you to all who
helped test and verify. I'll start publishing the release and client libs
shortly

-Jake




On Sun, Aug 18, 2013 at 8:11 PM, Jake Farrell  wrote:

> All,
> I propose that we accept the following release candidate as the official
> Apache Thrift 0.9.1 release.
>
> http://people.apache.org/~jfarrell/thrift/0.9.1/thrift-0.9.1-rc.tar.gz
>
>
> The release candidate is created from the 0.9.1 branch and can be cloned
> using:
> git clone -b 0.9.1 http://git-wip-us.apache.org/repos/asf/thrift.git
>
> The release candidates GPG signature can be found at:
> http://people.apache.org/~jfarrell/thrift/0.9.1/thrift-0.9.1-rc.tar.gz.asc
> It has an MD5 sum of 8a8dd3e84bd59bfe33f7f07e931248a1
>
> The CHANGES list for this release is available at:
>
> https://git-wip-us.apache.org/repos/asf?p=thrift.git;a=tree;h=refs/heads/0.9.1;hb=0.9.1
>
> Client libraries are available for testing at:
> http://people.apache.org/~jfarrell/thrift/0.9.1/lib/
>
> The deb packages are available at:
> http://people.apache.org/~jfarrell/thrift/0.9.1/contrib/deb/
>
> The windows compiler is available at:
> http://people.apache.org/~jfarrell/thrift/0.9.1/windows/
>
>
> Please download, verify sig/sum, and install/test the libraries of your
> choice.
>
> This vote will close in 72 hours.
>
> -Jake
>

[Announcement] New Committer: Ben Craig

[Jake Farrell]

On behalf of the Apache Thrift PMC, I would like to welcome our newest
committer to the project:

  Ben Craig

He has been extremely active contributing quality patches which have
advanced the client libraries, and commenting in the user and dev mailing
lists providing feedback and assistance to new comers. It is my honor to
welcome him as a committer.

Congratulations and thank you for your hard work


Jake Farrell
Apache Thrift PMC

Mavenizing the java builds

[Jake Farrell]

I have been playing with the idea of converting all libs and contrib items
that use java and ant over to using maven for the build process. I am
mainly interested in this to gain one common parent pom which will allow us
not to have redundant information in multiple locations as it is now within
each build.xml and will make releasing all java based artifacts easier for
me.

I have converted over the following items as a proof of concept and they
are all located in lib/java folder within my mavenize branch available at
https://github.com/jfarrell/thrift/tree/mavenize

* java lib
* thrift-maven-plugin
* as3 lib
* fb303 lib

I would love to get everyones feedback on this

Thanks
-Jake

Re: AW: Easy installer for Thrift in Windows

[Jake Farrell]

Hey Andrew
Thanks for finding it and pointing it out, this would be useful to a lot of
windows users. I'll reach out to them

-Jake



On Wed, Sep 25, 2013 at 10:06 AM, Andrew Pennebaker
wrote:

> Apologies if I misspoke. I did not submit the installer, I just happened to
> notice that it exists. If we send a gentle note on the Contact
> Ownerspage, we
> can get some information on the installer source, maybe fork it
> and comb through it.
>
> I understand Apache's policy limiting external download links, no getting
> around that. I think we can work together to get an official Apache Thrift
> Windows installer listed on the official installation tutorial, especially
> now that it's proven technologically possible.
>
>
> On Tue, Sep 24, 2013 at 3:58 PM, Joseph Schaefer  >wrote:
>
> > No such policy that I'm aware of.  All you need do is distinguish between
> > official release artifacts and convenience artifacts that you may not
> > control.
> >
> > Sent from my iPhone
> >
> > > On Sep 24, 2013, at 3:52 PM, "Roger Meier" 
> > wrote:
> > >
> > > Andrew ,
> > > this is great!
> > >
> > > I really like that simplification of install on the Windows platform.
> > >
> > > Adding such external download is not compatible with the Apache
> Policies
> > as
> > > far as I know.
> > > That's why we removed links to latest builds from the download page :-(
> > >
> > > Would be great to have your patches used to make NuGet within the
> Apache
> > > Thrift code base.
> > > "generate a .MSI that installs the thrift compiler and runtime
> > libraries" is
> > > a wish since 2010...
> > > https://issues.apache.org/jira/browse/THRIFT-874
> > >
> > > Let's use apt-get like SUPER COW POWER on windows by using NuGet and
> > > chocolatey packaging.
> > >
> > > all the best!
> > > roger
> > > ;-r
> > >
> > >
> > >
> > >
> > >> -Ursprüngliche Nachricht-
> > >> Von: Ben Craig [mailto:bencr...@apache.org]
> > >> Gesendet: Dienstag, 24. September 2013 20:40
> > >> An: u...@thrift.apache.org
> > >> Betreff: Re: Easy installer for Thrift in Windows
> > >>
> > >> I'm glad to see the thrift compiler get added to chocolatey.  I've
> been
> > > talking
> > >> with some of the Boost maintainers about getting official NuGet
> support
> > > for
> > >> the Boost libraries.  Once that happens, I intend on getting NuGet
> > support
> > >> added for the Thrift libraries.
> > >>
> > >> Note that I'm not making any promises as to which release that will go
> > in.
> > >> It's just something I've been researching.
> > >>
> > >>
> > >>
> > >> From:   Andrew Pennebaker 
> > >> To: Thrift Users ,
> > >> Date:   09/24/2013 12:43 PM
> > >> Subject:Easy installer for Thrift in Windows
> > >>
> > >>
> > >>
> > >> A Chocolatey-style installer for Thrift has been published for Windows
> > >> users:
> > >>
> > >> http://chocolatey.org/packages?q=thrift
> > >>
> > >> Could we include a link to this at the top of the Windows Thrift
> install
> > > tutorial?
> > >>
> > >> http://thrift.apache.org/docs/install/windows/
> > >>
> > >> Now it's much easier for Windows users to setup Thrift!
> > >
> > >
> >
>

Re: thrift pull request: Defensively copy binary fields (THRIFT-2233)

[Jake Farrell]

Hi Andrew
First I want to thank you for taking the time to contribute, your help is
greatly appreciated.

For pull requests from Github, we (Apache Thrift) do not accept them
because there is no mechanism in place currently that grants use of that
code to the ASF for that pull request. Also Github is only a mirror of our
official code repository, so we can not accept, merge and close the pull
request via Github. Also only a limited number of people are part of the
Apache organization on Github which is why we have 60+ open pull requests
currently.

We have kept the process the same for how we accept contributions from when
we incubated to current. There are discussions and work underway in @infra
to help with closing and accepting pull requests from Github, but currently
we take all contributions via jira tickets and attachments.

The pull requests you issue from Github do not add noise to the dev@ list
as they are moderated out and only the moderators will see the actual pull
request message come through. If it helps you better track your
contributions please continue to do so.

-Jake





On Tue, Oct 22, 2013 at 1:09 PM, Andrew Gaul  wrote:

> Ben, I have opened JIRA issues with attachments for all of my patches.
> I open the in GitHub pull request to allow for review comments and for
> my own tracking purposes.  If the PR adds too much noise I will
> discontinue this practice.  Let me know how to best contribute.
>
> (Inaccurate to say that Thrift can't accept pull requests.  Other Apache
> projects including jclouds which I contribute to use JIRA for issue
> tracking and GitHub for code.  Most code has a JIRA issue except for
> smaller, cleanup commits.)
>
> On Tue, Oct 22, 2013 at 08:47:53AM -0500, Ben Craig wrote:
> > Thanks you for your interest Andrew.  Unfortunately, we can't currently
> > accept git pull requests.  We only accept patches attached to JIRA
> > tickets.  For more information on how to get changes into Thrift, see the
> > following page:
> > http://thrift.apache.org/docs/HowToContribute/
> >
> > andrewgaul  wrote on 10/22/2013 01:04:03 AM:
> >
> > > From: andrewgaul 
> > > To: dev@thrift.apache.org,
> > > Date: 10/22/2013 08:22 AM
> > > Subject: thrift pull request: Defensively copy binary fields
> > (THRIFT-2233)
> > >
> > > GitHub user andrewgaul opened a pull request:
> > >
> > > https://github.com/apache/thrift/pull/60
> > >
> > > Defensively copy binary fields (THRIFT-2233)
> > >
> > > This ensures that one consumer of a ByteBuffer does not interfere
> > with
> > > another, e.g.,
> > >
> > > MyStruct myStruct = ...;
> > > byte[] array = new byte[myStruct.bufferForValue().capacity()];
> > > someStruct.bufferForValue().get(array);
> > > someStruct.bufferForValue().get(array);  // previously, NPE
> > >
> > > You can merge this pull request into a Git repository by running:
> > >
> > > $ git pull https://github.com/maginatics/thrift defensive-copy
> > >
> > > Alternatively you can review and apply these changes as the patch at:
> > >
> > > https://github.com/apache/thrift/pull/60.patch
> > >
> > > 
> > > commit 5f7545b1dcd0d94724bc41cfb41bef0d7d4c869d
> > > Author: Andrew Gaul 
> > > Date:   2013-10-22T00:38:15Z
> > >
> > > Defensively copy binary fields (THRIFT-2233)
> > >
> > > This ensures that one consumer of a ByteBuffer does not interfere
> > with
> > > another, e.g.,
> > >
> > > MyStruct myStruct = ...;
> > > byte[] array = new byte[myStruct.bufferForValue().capacity()];
> > > someStruct.bufferForValue().get(array);
> > > someStruct.bufferForValue().get(array);  // previously, NPE
> > >
> > > 
> > >
>
> --
> Andrew Gaul
> http://gaul.org/
>

Re: Looking for +1 on a JIRA and add to contributor list

[Jake Farrell]

Hi Venki
Thanks for the patch, appreciate the help. I will take a look at it and
review

-Jake


On Sun, Oct 27, 2013 at 2:48 PM, Venki Korukanti
wrote:

> Hi,
>
> I have created JIRA
> THRIFT-2122 and
> attached a patch that includes fix and unittest. Looking for a +1 to
> commit.
>
> I am not sure what is the criteria for adding to contributors list. If
> possible could you please add me to the contributors list? I have one more
> bug in SSL area that I am currently working on fixing.
>
> Thanks
> Venki
>

Re: introduction from Maginatics

[Jake Farrell]

Hi Andrew
You are doing everything I would recommend. Join and participate on the
mailing list, work on patches and help review others, and help answer any
question new users might have. Appreciate the help

-Jake


On Mon, Nov 11, 2013 at 2:01 PM, Andrew Gaul  wrote:

> I submitted a few patches to Thrift recently and want to introduce
> myself.  I work at Maginatics and we use Thrift to communicate between
> C++, Java, and Ruby processes in our cloud file system.  Our team has
> used Thrift since 2011 and several engineers have submitted patches.
> Upstream accepted many of them but we still apply patches to our local
> Thrift.  Presently we run 0.9.0 and apply:
>
> THRIFT-1458 (committed in 0.9.1)
> THRIFT-1528
> THRIFT-1630 (committed in 0.9.1)
> THRIFT-1676
> THRIFT-1740 (committed in 0.9.1)
> THRIFT-1815 (committed in master)
> THRIFT-1837 (committed in 0.9.1)
> THRIFT-1845 (committed in 0.9.1)
> THRIFT-1846 (committed in 0.9.1)
> THRIFT-1992 (committed in 0.9.1)
> THRIFT-2037 (committed in master)
> THRIFT-2048 (committed in master)
>
> We plan to rebase to 0.9.1 and apply:
>
> THRIFT-2172
> THRIFT-2193
> THRIFT-2227
> THRIFT-2233
> THRIFT-2238
> THRIFT-2260
>
> I would like to bring our code closer to mainline, similar to our
> relationship with Apache jclouds.  I appreciate any suggestions on how
> to work better with Thrift and increase participation from Maginatics.
> Specifically I can help with the Java bindings and my colleague Nate
> Rosenblum can help with the C++ bindings.  I look forward to continuing
> to work together!
>
> --
> Andrew Gaul
> http://maginatics.com/
>

[REPORT] Apache Thrift

[Jake Farrell]

Jan 2014

Thrift is a framework for providing cross-platform RPC and serialization.

Project Status
-
The Apache Thrift community continues to see consistent growth with
submissions
from new contributors for bug fixes and client library improvements.

Community
---
Latest Additions:

* PMC addition:   Jens Geyer, 5.02.2013
* Contributor addition:   Ben Craig, 8.23.2013

Issue backlog status since last report:

* Created: 89
* Resolved: 76

Mailing list activity since last report:

* @dev   946 messages
* @user  96 messages

Releases
---
Last release: 0.9.1, Release Date: Aug 21, 2013

We are preparing for our next release candidate and addressing build issues
seen
across different platforms. Our 0.9.2 release will be focused on client
library
additions, easier build options and enhanced unit tests.

Re: AW: thrift pull request: README update

[Jake Farrell]

Travis hook is now enabled

-Jake


On Fri, Jan 10, 2014 at 7:04 PM, Roger Meier wrote:

> I've sent a request on Apache infra mailing list to enable enable GitHub
> Service Hook for travis-ci.
>
> -roger
>
> Quoting Jens Geyer :
>
>  Hi,
>>
>> we highly appreciate quality patches. Unfortunately, for legal reasons we
>> cannot accept pull requests yet.
>>
>> Please file a Jira ticket and add the patch there. The whole (short)
>> process
>> is outlined at http://thrift.apache.org/docs/HowToContribute .
>>
>> Thanks again,
>> JensG
>>
>> 
>> Von: emchristiansen
>> Gesendet: 10.01.2014 00:05
>> An: dev@thrift.apache.org
>> Betreff: thrift pull request: README update
>>
>> GitHub user emchristiansen opened a pull request:
>>
>> https://github.com/apache/thrift/pull/74
>>
>> README update
>>
>> Updates README to include a Travis build badge, which requires
>> renaming
>> it to README.md.
>> Also fixed some things in the readme.
>>
>> Important note: The link for the build badge is apparently inactive.
>> Either this project hasn't been registered with Travis CI, or it is
>> registered under a different name.
>> In the former case, please do register the project.
>> In the latter case, please amend this pull request so the badge link
>> points to the correct address.
>>
>> You can merge this pull request into a Git repository by running:
>>
>> $ git pull https://github.com/emchristiansen/thrift travis
>>
>> Alternatively you can review and apply these changes as the patch at:
>>
>> https://github.com/apache/thrift/pull/74.patch
>>
>> 
>> commit ed32cce0809b441b4b3abb9c425c7385c8052c18
>> Author: Eric Martin Christiansen 
>> Date:   2014-01-08T22:23:31Z
>>
>> added build badge
>>
>> commit 1c5a56bb59fea3c06c5f07153fe7d04561a805b7
>> Author: Eric Martin Christiansen 
>> Date:   2014-01-09T20:50:34Z
>>
>> typo
>>
>> commit fe5759a5a50550f7f5db665c65c4a8b51d14468c
>> Author: Eric Martin Christiansen 
>> Date:   2014-01-09T20:51:43Z
>>
>> rename README
>>
>> commit 430574919a22c46c1cbf120d54f2259358c09938
>> Author: Eric Martin Christiansen 
>> Date:   2014-01-09T22:59:23Z
>>
>> markdown niceties
>>
>> 
>>
>
>

Re: Re: [jira] [Commented] (THRIFT-2190) Add the JavaScript thrift.js lib to the Bower registry

[Jake Farrell]

These new tags are redundant and I would prefer that we just rename the
tags that existed rather than duplicating with the comment semver.

I'll update the process and clean up the existing tags and we can include
the js package in the release process for submitting to bower.

-Jake




On Sun, Feb 2, 2014 at 3:25 PM, Randy Abernethy
wrote:

> Hey Henrique and Roger,
>
> Super great to move the Bower initiative forward. Regarding what we should
> publish over Bower,
> I think it should be the necessary bits for front end development.
>-  lib/js/dist/README.md
>-  lib/js/dist/thrift.js
>-  lib/js/dist/thrift.min.js
>-  lib/js/dist/bower.json
>
> The README.md needs to be updated and emitted in the grunt build along with
> the bower file
> but otherwise we're there.
>
> Here's a session using bower to add AngularJS to a front end web project.
> AngularJS
> is a pretty well respected MVC framework from Google and the files they
> include in their
> Bower deployment are a good approximation of what the community might be
> expecting.
> Globally replace the word "angular" with the word "thrift" and I think you
> have a good model.
>
> -Randy
>
> 
> Randy@VAVAU /d/dev/test/bt
> $ bower install angular
> bower angular#* cached git://
> github.com/angular/bower-angular.git#1.0.8
> bower angular#*   validate 1.0.8 against git://
> github.com/angular/bower-angular.git#*
> bower angular#*new version for git://
> github.com/angular/bower-angular.git#*
> bower angular#*resolve git://
> github.com/angular/bower-angular.git#*
> bower angular#*   download
> https://github.com/angular/bower-angular/archive/v1.2.10.tar.gz
> bower angular#*extract archive.tar.gz
> bower angular#*   resolved git://
> github.com/angular/bower-angular.git#1.2.10
> bower angular#~1.2.10  install angular#1.2.10
>
> angular#1.2.10 bower_components\angular
>
> Randy@VAVAU /d/dev/test/bt
> $ ls -l bower_components/angular/
> total 557
> -rw-r--r--1 RandyAdminist 1615 Feb  2 12:08 README.md
> -rw-r--r--1 RandyAdminist  241 Feb  2 12:08 angular-csp.css
> -rw-r--r--1 RandyAdminist   727582 Feb  2 12:08 angular.js
> -rw-r--r--1 RandyAdminist   100085 Feb  2 12:08 angular.min.js
> -rw-r--r--1 RandyAdminist36933 Feb  2 12:08 angular.min.js.gzip
> -rw-r--r--1 RandyAdminist   269869 Feb  2 12:08 angular.min.js.map
> -rw-r--r--1 RandyAdminist   98 Feb  2 12:08 bower.json
>
> 
>
>
>
>
>
>
>
> On Sun, Feb 2, 2014 at 11:10 AM, Henrique Mendonça  >wrote:
>
> > Awesome Roger, thanks heaps!
> >
> > Randy, do you have anything to add/amend on my bower file? I'm not sure
> if
> > we should ignore all the other libraries, compiler, etc, should we?
> > Although it's not JS at all, perhaps the user might want to build the
> > compiler/tests... what do you guys think?
> > Anyway, if you have a bower file you can attach it to the ticket here I'd
> > be happy to commit and register it. "thrift" seems to be still available
> :)
> >
> > Cheers,
> > Henrique
> >
> >
> > On 2 February 2014 18:16, Roger Meier  wrote:
> >
> > > There is now real reason for "thrift-" prefix within tag name.
> > > Bryan did this and Jake as well, however we all already agree on the
> > semver
> > > concept.
> > > See http://thrift.apache.org/docs/committers/HowToVersion
> > >
> > > So I added these signed semver tags:
> > > 0.2.0
> > > 0.3.0
> > > 0.4.0
> > > 0.6.0
> > > 0.7.0
> > > 0.8.0
> > > 0.9.0
> > > 0.9.1
> > >
> > >
> > > We should add the bower.json file to the root folder
> > >
> > > -roger
> > >
> > >
> > > -Original Message-
> > > From: hmendo...@gmail.com [mailto:hmendo...@gmail.com] On Behalf Of
> > > Henrique Mendonça
> > > Sent: Sonntag, 2. Februar 2014 13:43
> > > To: dev@thrift.apache.org
> > > Subject:  SPAM [ 7.901 ]  Re: [jira] [Commented] (THRIFT-2190)
> > Add
> > > the JavaScript thrift.js lib to the Bower registry
> > >
> > > Hi Randy,
> > >
> > > I think you can test it with your own fork like:
> > > https://github.com/henrique/thrift/blob/master/bower.json
> > > bower install https://github.com/henrique/thrift.git
> > >
> > > I don't really use bower so I am not sure if this reference to
> > /lib/js/src
> > > works. However, if it does we would only need to have standard semver
> > tags
> > > the official git repo. Our current tags from 0.6 always start with
> > > "thrift-"
> > > so bower only recognizes 0.5.0 on the current repo. We'd need to add
> new
> > > tags like in http://semver.org/ : "M.M.P" or "vM.M.P"
> > >
> > > @Jake&Roger: why did we start appending thrift- to our tags after 0.5?
> > >
> > > Cheers,
> > > Henrique
> > >
> > >
> > > On 1 February 2014 22:28, Randy Abernethy (JIRA) 
> > wrote:
> > >
> > > >
> > > > [
> > > >
> https://issues.apache.org/jira/browse/THRIFT-2190?page=com.atlassian.j
> > > >
> ira.plugin.system.issuetabpanels:comm

Re: About GSoC project Idea "Test Framework harmonization across all languages"

[Jake Farrell]

Hey Chris
The cross language tests should only be in the /test folder. The /lib/go
folder should contain the test cases specific to the go lib implementation.
Appreciate the work on this

-Jake



On Sun, Mar 2, 2014 at 1:48 PM, Chris Bannister wrote:

> Hi Jens,
>
> Thanks for the pointers. Reading THRIFT-35, do you mean to have the
> compiled parts in /lib/go but to have the cross language server/client in
> /test? Or is it the intention that the cross language test will move to
> /lib/go?
>
> Chris
>
> On 2 March 2014 14:35, Jens Geyer  wrote:
>
> > Hi Chris,
> >
> > that's great, many thanks for both: starting on this, and the feedback
> > about it.
> >
> > There is already a "test" directory at /lib/go, which is the preferred
> > place, rather than /test. The latter is something that we strive to
> remove
> > completely, see THRIFT-35.  In that test directory, have a look at
> > makefile.am, which should already set up the go path etc.
> >
> > Does that answer your question? Don't hesitate to ask, I'll give as much
> > support as needed/possible. Integrating Go with the suite becomes more
> and
> > more important.
> >
> > Have fun,
> > JensG
> >
> >
> >
> > -Ursprüngliche Nachricht- From: Chris Bannister
> > Sent: Sunday, March 2, 2014 11:48 AM
> > To: dev@thrift.apache.org
> > Subject: Re: About GSoC project Idea "Test Framework harmonization across
> > all languages"
> >
> >
> > Hi Jens,
> >
> > I had started working on a test client/server for go but stopped at the
> > point where I needed to have the IDL's compiled as my knowledge of the
> > build system and how to set it up for go is lacking,
> > here is a basic server skeleton, if you could advise on how to setup the
> > build system to compile and setup the gopath I would be willing to
> continue
> > with this.
> >
> > https://github.com/Zariel/thrift/commits/golang-tests
> >
> >
> >
> > On 2 March 2014 09:24, Jens Geyer  wrote:
> >
> >  Hi Roger,
> >>
> >> I don't know exactly what you have in mind but we could really need Go
> >> connected to the test suite.
> >>
> >> Biggest obstacle is that there is no Test server/client yet. So if by
> any
> >> chance ... ;-)
> >>
> >> Have fun,
> >> JensG
> >> 
> >> Von: Roger Meier
> >> Gesendet: 01.03.2014 14:51
> >> An: 'Chamila Wijayarathna'; dev@thrift.apache.org
> >> Betreff: RE: About GSoC project Idea "Test Framework harmonization
> across
> >> all languages"
> >>
> >> Hi Chamila
> >>
> >>
> >>
> >> Yes, I would like to improve the cross language and platform test
> >> suite(THRIFT-847), documentation and QA further with GSoC 2014.
> >>
> >> I was not aware of WSO2, seems to be a real Apache friend!
> >> http://wso2.com/apache
> >>
> >>
> >>
> >> The goal of this GSoC task is:
> >>
> >> * Cover any possible language, protocol, transport, type, etc.
> >> vice
> >> versa(Just a few are integrated right now)
> >>
> >> * Port cross language test suite to non linux systems
> >>
> >> * Improve test and functionality reporting towards features list
> >> for
> >> the web site
> >>
> >> * Fix documentation
> >>
> >> * Quality in general
> >>
> >> * Help to make it perfect. I'm sure there is enough to do;-)
> >>
> >>
> >>
> >> All the best!
> >>
> >> -roger
> >>
> >>
> >>
> >>
> >>
> >> From: Chamila Wijayarathna [mailto:cdwijayarat...@gmail.com]
> >> Sent: Mittwoch, 26. Februar 2014 20:46
> >> To: dev@thrift.apache.org
> >> Cc: ro...@bufferoverflow.ch
> >> Subject: About GSoC project Idea "Test Framework harmonization across
> all
> >> languages"
> >>
> >>
> >>
> >> Hello all,
> >>
> >> I am a Computer Science and Engineering student at University of
> Moratuwa,
> >> Sri Lanka and I'm currently working as an intern at WSO2. I have worked
> >> with
> >> WSO2 CEP and WSO2 BAM which uses apache thrift. I am willing to
> contribute
> >> to the project "Test Framework harmonization across all languages" [1].
> >> Can
> >> I have some more information about what are the parts of this project
> that
> >> are still open and what things expected to done during GSoC period?
> >>
> >>
> >>
> >> Thank You!
> >>
> >>
> >>
> >>
> >> --
> >> Chamila Dilshan Wijayarathna,
> >> SMIEEE, SMIESL,
> >> Undergraduate,
> >> Department of Computer Science and Engineering,
> >> University of Moratuwa.
> >>
> >>
> >>
> >
>

Re: [jira] [Closed] (THRIFT-2001) http://thrift.apache.org/ Example "C++ Server" tab is broken

[Jake Farrell]

Hey Roger
I've been working on a version using middleman which I almost have
completed, I've found that it is better at rendering code snippets and docs
than nanoc and the layout and config within middleman is simplified over
what we currently have. Will throw up on my people.a.o account shortly

-Jake


On Tue, Mar 4, 2014 at 5:25 PM, Roger Meier  wrote:

> Just fixed this on the web site:
> URL: http://svn.apache.org/r1574224
> Log:
> content/index.md: no 4 spaces or tab to avoid md double rendering
> content/tutorial/cpp.md: use html entities < and >
>
> Could you verify site compile on your platforms?
>
> I think about a upgrade of nanoc and adding a code snippet include filter
> such as this:
> http://logs.drbig.one.pl/articles/using_nanoc_for_blogging.html
>
> -roger
>
>
> -Original Message-
> From: Jens Geyer [mailto:jensge...@hotmail.com]
> Sent: Mittwoch, 12. Februar 2014 20:07
> To: dev@thrift.apache.org
> Subject: Re: [jira] [Closed] (THRIFT-2001) http://thrift.apache.org/Example 
> "C++ Server" tab is broken
>
> Hi *,
>
> I had similar issues with the publishing process lately. Something is
> broken there, I guess. These sporadic erors make the whole process at least
> fragile, if not prone to error. I don't want to switch technology just for
> the fun of it, but I also don't want to live in constant fear every time
> whenever I change sth. on the web site.
>
> $0,02
> JensG
>
>
> -Ursprüngliche Nachricht-
> From: Henrique Mendonça
> Sent: Wednesday, February 12, 2014 7:23 PM
> To: dev@thrift.apache.org
> Subject: Re: [jira] [Closed] (THRIFT-2001) http://thrift.apache.org/Example 
> "C++ Server" tab is broken
>
> Thanks again, Jake!
> I didn't get why it was like that again since the markdown file looked
> alright...
>
>
> On 12 February 2014 17:16, Jake Farrell (JIRA)  wrote:
>
> >
> >  [
> > https://issues.apache.org/jira/browse/THRIFT-2001?page=com.atlassian.j
> > ira.plugin.system.issuetabpanels:all-tabpanel]
> >
> > Jake Farrell closed THRIFT-2001.
> > 
> >
> > Resolution: Fixed
> >
> > > http://thrift.apache.org/ Example "C++ Server" tab is broken
> > > 
> > >
> > > Key: THRIFT-2001
> > > URL: https://issues.apache.org/jira/browse/THRIFT-2001
> > > Project: Thrift
> > >  Issue Type: Documentation
> > >  Components: Website
> > > Environment: Chrome, IE, Opera
> > >Reporter: Henrique Mendonça
> > >Assignee: Jake Farrell
> > > Fix For: 0.9.1
> > >
> > >
> > > The tabs on the homepage's example section doesn't work in any of my
> > browsers.
> > > Not sure what changed but it must be just html type something like
> that.
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v6.1.5#6160)
> >
>
>
>
>

Re: [jira] [Closed] (THRIFT-2001) http://thrift.apache.org/ Example "C++ Server" tab is broken

[Jake Farrell]

I think that we should keep the website and the code base separate. Having
the generated site that gets published via pubsub in the same location as
the website content makes things easier to find and debug.

I recently helped out Apache Mesos with their website and they update the
/documentation section of their website with content from the source repo.
If you look at the Rakefile in their site dir [1] you can see how it pulls
over the current documentation from the source code and updates the
documentation from it.

I have updated our site to do something similar for our tutorials so we do
not have to inject the entire website into the source code. I've also gone
ahead and updated our site with the source_inserter filter, modified for
our setup, and all is working as expected with the latest version of nanoc.
Tutorials are now available on the site [2] and how its accomplished [3].

As for switching generators i'm fine with Nanoc or Middleman. When I
initially reworked the website I used Jekyll and spent a fair amount of
time jumping through hoops to make the site not behave like a blog. From
reading the docs and what Octopress does I think that we would be in a
similar situation as we had with Jekyll. Nanoc is working right now and if
everyone is happy with it then we can stay as is.

-Jake


[1]: http://svn.apache.org/repos/asf/mesos/site/Rakefile
[2]: http://thrift.apache.org/tutorial/
[3]: http://svn.apache.org/repos/asf/thrift/site/content/tutorial/cpp.md





On Tue, Mar 4, 2014 at 6:36 PM, Roger Meier  wrote:

> Hi Jake & co!
>
> I was not aware of middleman, but I will have a closer look at it.
> Octopress is the other hot candidate I see on the radar.
>
> However, I played around with the mentioned source_inserter and it does a
> nice job.
> See the attached a patch with modified js tutorial and nanoc upgrade.
>
> What do you think about a short term solution with the nanoc upgrade and
> source_inserter?
>
> thrift_src  directory is currently defined within config.yaml, this can be
> changed to ./.. if we move site to www folder within source.
> The full site could be versioned via regular release process and the
> website
> will have up-to-date documentation and information consistant with each
> release. Development and Documentation in one place will simplify things.
> There are some README.md files within source that we can include directly
> via include filters and the upcoming cross.md compatibility/feature
> overview
> generated by the test suite.
>
> Best!
> -roger
>
> -Original Message-
> From: Jake Farrell [mailto:jfarr...@apache.org]
> Sent: Dienstag, 4. März 2014 23:47
> To: dev@thrift.apache.org
> Subject: Re: [jira] [Closed] (THRIFT-2001) http://thrift.apache.org/Example
> "C++ Server" tab is broken
>
> Hey Roger
> I've been working on a version using middleman which I almost have
> completed, I've found that it is better at rendering code snippets and docs
> than nanoc and the layout and config within middleman is simplified over
> what we currently have. Will throw up on my people.a.o account shortly
>
> -Jake
>
>
> On Tue, Mar 4, 2014 at 5:25 PM, Roger Meier 
> wrote:
>
> > Just fixed this on the web site:
> > URL: http://svn.apache.org/r1574224
> > Log:
> > content/index.md: no 4 spaces or tab to avoid md double rendering
> > content/tutorial/cpp.md: use html entities < and >
> >
> > Could you verify site compile on your platforms?
> >
> > I think about a upgrade of nanoc and adding a code snippet include
> > filter such as this:
> > http://logs.drbig.one.pl/articles/using_nanoc_for_blogging.html
> >
> > -roger
> >
> >
> > -Original Message-
> > From: Jens Geyer [mailto:jensge...@hotmail.com]
> > Sent: Mittwoch, 12. Februar 2014 20:07
> > To: dev@thrift.apache.org
> > Subject: Re: [jira] [Closed] (THRIFT-2001)
> > http://thrift.apache.org/Example "C++ Server" tab is broken
> >
> > Hi *,
> >
> > I had similar issues with the publishing process lately. Something is
> > broken there, I guess. These sporadic erors make the whole process at
> > least fragile, if not prone to error. I don't want to switch
> > technology just for the fun of it, but I also don't want to live in
> > constant fear every time whenever I change sth. on the web site.
> >
> > $0,02
> > JensG
> >
> >
> > -----Ursprüngliche Nachricht-
> > From: Henrique Mendonça
> > Sent: Wednesday, February 12, 2014 7:23 PM
> > To: dev@thrift.apache.org
> > Subject: Re: [jira] [Closed] (THRIFT-2001)
> > http://thrift.apache.org/Example "C++ Server" tab is broken
>

Re: [jira] [Closed] (THRIFT-2001) http://thrift.apache.org/ Example "C++ Server" tab is broken

[Jake Farrell]

I've fixed the versions in the Gemfile as below to avoid this type of
issue, updates committed

-Jake


gem 'rake'
gem 'nanoc', '3.6.7'
gem 'redcarpet', '3.1.1'
gem 'coderay', '1.1.0'
gem 'adsf', '1.2.0'
gem 'nokogiri', '1.6.1'
gem 'less', '2.5.0'
gem 'mime-types', '2.1'
gem 'therubyracer', '0.12.1'




On Wed, Mar 5, 2014 at 3:43 AM, Roger Meier  wrote:

> Hi Jake
>
> Great job!
>
> > -Original Message-
> > From: Jake Farrell [mailto:jfarr...@apache.org]
> > Sent: Mittwoch, 5. März 2014 06:47
> > To: dev@thrift.apache.org
> > Subject:  SPAM [ 7.9 ]  Re: [jira] [Closed] (THRIFT-2001)
> > http://thrift.apache.org/ Example "C++ Server" tab is broken
> >
> > I think that we should keep the website and the code base separate.
> Having
> > the generated site that gets published via pubsub in the same location as
> the
> > website content makes things easier to find and debug.
> I'm ok with this.
>
> >
> > I recently helped out Apache Mesos with their website and they update the
> > /documentation section of their website with content from the source
> repo.
> > If you look at the Rakefile in their site dir [1] you can see how it
> pulls
> over the
> > current documentation from the source code and updates the
> > documentation from it.
> Nice approach and good alternative to www within src.
>
> >
> > I have updated our site to do something similar for our tutorials so we
> do
> not
> > have to inject the entire website into the source code. I've also gone
> ahead
> > and updated our site with the source_inserter filter, modified for our
> setup,
> > and all is working as expected with the latest version of nanoc.
> > Tutorials are now available on the site [2] and how its accomplished [3].
> Less redundancy and more consistency for the documentation.
> That's exactly what I was looking for. I used the same filter code base on
> my patch.
>
> >
> > As for switching generators i'm fine with Nanoc or Middleman. When I
> > initially reworked the website I used Jekyll and spent a fair amount of
> time
> > jumping through hoops to make the site not behave like a blog. From
> reading
> > the docs and what Octopress does I think that we would be in a similar
> > situation as we had with Jekyll. Nanoc is working right now and if
> everyone is
> > happy with it then we can stay as is.
> Yes, we spent lot of time with nanoc and each new systems adds new
> issues:-(
> It's easier to improve what we have. I guess nanoc is still a very active
> project.
>
> I still have different output when generating the site... is this os
> dependent?!
>
> Could you please check the attached nanoc_upgrade.patch and generate the
> site
> on your os?
> I guess it is worth to upgrade to the latest nanoc and become able to use
> more
> recent features of nanoc.
>
> Greetings!
> -roger
>
> >
> > -Jake
> >
> >
> > [1]: http://svn.apache.org/repos/asf/mesos/site/Rakefile
> > [2]: http://thrift.apache.org/tutorial/
> > [3]: http://svn.apache.org/repos/asf/thrift/site/content/tutorial/cpp.md
> >
> >
> >
> >
> >
> > On Tue, Mar 4, 2014 at 6:36 PM, Roger Meier 
> > wrote:
> >
> > > Hi Jake & co!
> > >
> > > I was not aware of middleman, but I will have a closer look at it.
> > > Octopress is the other hot candidate I see on the radar.
> > >
> > > However, I played around with the mentioned source_inserter and it
> > > does a nice job.
> > > See the attached a patch with modified js tutorial and nanoc upgrade.
> > >
> > > What do you think about a short term solution with the nanoc upgrade
> > > and source_inserter?
> > >
> > > thrift_src  directory is currently defined within config.yaml, this
> > > can be changed to ./.. if we move site to www folder within source.
> > > The full site could be versioned via regular release process and the
> > > website will have up-to-date documentation and information consistant
> > > with each release. Development and Documentation in one place will
> > > simplify things.
> > > There are some README.md files within source that we can include
> > > directly via include filters and the upcoming cross.md
> > > compatibility/feature overview generated by the test suite.
> > >
> > > Best!
> &

Re: [jira] [Closed] (THRIFT-2001) http://thrift.apache.org/ Example "C++ Server" tab is broken

[Jake Farrell]

Unsure why its doing that for you, the lib/html_sitemap grabs all children
and sorts them by the downcase of the name, so what you are showing below
is incorrect as its placing about after downloads. I'm on OS X and running
the calls through bundler, bundle install && bundle exec rake gen. Added
rake version to Gemfile

-Jake



On Wed, Mar 5, 2014 at 9:53 AM, Roger Meier  wrote:

> There is just one diff left when I regenerate:
>
> $ svn diff
> Index: publish/sitemap/index.html
> ===
> --- publish/sitemap/index.html  (revision 1574509)
> +++ publish/sitemap/index.html  (working copy)
> @@ -71,7 +71,7 @@
>  Home
>  
>
> -About
> +Download
>
>  Developers
>
> @@ -87,7 +87,7 @@
>  
>  
>
> -Download
> +About
>
>  Mailing Lists
>
>
> Any idea?
>
> -roger
>
>
> PS: Any reason for not defining a rake version? e.g. gem 'rake', '10.1.1'
>
>
>
> From: Jake Farrell [mailto:jfarr...@apache.org]
> Sent: Mittwoch, 5. März 2014 15:07
> To: Roger Meier
> Cc: dev@thrift.apache.org; jfarr...@apache.org
> Subject: Re: [jira] [Closed] (THRIFT-2001) http://thrift.apache.org/Example
> "C++ Server" tab is broken
>
> I've fixed the versions in the Gemfile as below to avoid this type of
> issue,
> updates committed
>
> -Jake
>
>
> gem 'rake'
> gem 'nanoc', '3.6.7'
> gem 'redcarpet', '3.1.1'
> gem 'coderay', '1.1.0'
> gem 'adsf', '1.2.0'
> gem 'nokogiri', '1.6.1'
> gem 'less', '2.5.0'
> gem 'mime-types', '2.1'
> gem 'therubyracer', '0.12.1'
>
>
>
> On Wed, Mar 5, 2014 at 3:43 AM, Roger Meier 
> wrote:
> Hi Jake
>
> Great job!
>
> > -Original Message-
> > From: Jake Farrell [mailto:jfarr...@apache.org]
> > Sent: Mittwoch, 5. März 2014 06:47
> > To: dev@thrift.apache.org
> > Subject:  SPAM [ 7.9 ]  Re: [jira] [Closed] (THRIFT-2001)
> > http://thrift.apache.org/ Example "C++ Server" tab is broken
> >
> > I think that we should keep the website and the code base separate.
> Having
> > the generated site that gets published via pubsub in the same location as
> the
> > website content makes things easier to find and debug.
> I'm ok with this.
>
> >
> > I recently helped out Apache Mesos with their website and they update the
> > /documentation section of their website with content from the source
> repo.
> > If you look at the Rakefile in their site dir [1] you can see how it
> pulls
> over the
> > current documentation from the source code and updates the
> > documentation from it.
> Nice approach and good alternative to www within src.
>
> >
> > I have updated our site to do something similar for our tutorials so we
> do
> not
> > have to inject the entire website into the source code. I've also gone
> ahead
> > and updated our site with the source_inserter filter, modified for our
> setup,
> > and all is working as expected with the latest version of nanoc.
> > Tutorials are now available on the site [2] and how its accomplished [3].
> Less redundancy and more consistency for the documentation.
> That's exactly what I was looking for. I used the same filter code base on
> my patch.
>
> >
> > As for switching generators i'm fine with Nanoc or Middleman. When I
> > initially reworked the website I used Jekyll and spent a fair amount of
> time
> > jumping through hoops to make the site not behave like a blog. From
> reading
> > the docs and what Octopress does I think that we would be in a similar
> > situation as we had with Jekyll. Nanoc is working right now and if
> everyone is
> > happy with it then we can stay as is.
> Yes, we spent lot of time with nanoc and each new systems adds new
> issues:-(
> It's easier to improve what we have. I guess nanoc is still a very active
> project.
>
> I still have different output when generating the site... is this os
> dependent?!
>
> Could you please check the attached nanoc_upgrade.patch and generate the
> site
> on your os?
> I guess it is worth to upgrade to the latest nanoc and become able to use
> more
> recent features of nanoc.
>
> Greetings!
> -roger
>
> >
> > -Jake
> >
> >
> > [1]: http://svn.apache.org/repos/asf/mesos/site/Rakefile
> > [2]: http://thrift.apac

Re: actionscript client

[Jake Farrell]

Hi Dimat
Thank you for your interest in contributing back to Apache Thrift. Details
on submitting patches are available here [1]. The website source is
available here [2] and tutorial code is pulled from our source repo
/tutorials/* files. If you have any questions please let me know

-Jake


[1]: http://thrift.apache.org/docs/HowToContribute/
[2]: http://svn.apache.org/repos/asf/thrift/site/



On Wed, Mar 5, 2014 at 3:25 PM, Dimat Levchenko  wrote:

> hello,
>
> i am trying to use actionscript 3.0 thrift client with java server.
>
> on java part, i used tutorial example with TServerSocket as transport and
> TSimpleServer as server (i am newbee, so this information might be useless
> or incomplete...)
> on as3 part i found relevant TBinaryProtocol for protocol, and only, but
> not so relevent, TFullDuplexHttpClient for transport.
>
> Consequently i had problems with writing/reading binary data (transport
> problems, as i understand), for client is Http, but server is raw binary.
>
> so, i have 3 questions:
>
> 1. what i did wrong, and how i can use existing classes to make java work
> with as3 ?
>
> 2. i removed http-related parts from TFullDuplexHttpClient class in as3,
> and it now works fine with java TSimpleServer. can i contribute this class
> ?
>
> 3. how can i contribute to thrift website ? i would like to add description
> to tutorials about my experience, but i cannot find the way to do this :(
>
> thank you
>

Re: source doc to website

[Jake Farrell]

Hey Roger
Excellent discussion thread to start, this is one key area we have
struggled with for awhile.

Thoughts on moving them all into /docs and naming them appropriately? I
think this would be a better approach and make it easier to link and cross
reference between the docs and would make it easier to add all of them into
/docs on the website. Having all of the documentation spread across the
codebase will also make small updates harder and for new users to search
for information. If everyone is in favor of the README.md files in each
specific location then we can come up with something to map and filter them
into content for the website.

On a related note, what does everyone think of removing /test and using
/tutorials for cross language testing instead. This could make the
tutorials more robust and keep from having duplicate code samples in tests
and tutorials.

-Jake



On Wed, Mar 5, 2014 at 4:45 PM, Roger Meier  wrote:

> Hi Jake & co
>
> Do you have any trick to integrate some readme's located within the source
> tree?
>
> Source file:  Web Site URL:
> test/README.md thrift.apache.org/test
> test/STATUS.md
> thrift.apache.org/test/status
> test/keys/README.md  thrift.apache.org/test/keys
> lib//README.md thrift.apache.org/lib/
> lib//test/README.md   thrift.apache.org/lib//test
> lib//examples/README.md   thrift.apache.org/lib//examples
> compiler/cpp/README  thrift.apache.org/compiler
> debian/README
> thrift.apache.org/debian
> contrib//README thrift.apache.org/
>
> Name consistency is another topic...
> What about renaming all README files to README.md and start use markdown
> all
> over?
>
> Other stuff to integrate or align in some way:
> ./tutorial/README
> ./tutorial/erl/README
> ./tutorial/java/README
> ./tutorial/ocaml/README
> ./README
>
> All the best!
> -roger
>
>

Re: Contributions

[Jake Farrell]

Hi Dimat
Apache Infrastructure currently does not have a Gerrit installation and
there are no immediate plans to use it. We have Reviewboard setup for
Apache Thrift, but do not utilize it in out typical workflows. Right now
the preferred approach is to attach patchs to tickets with in the ASF jira.

http://thrift.apache.org/docs/HowToContribute/

-Jake


On Fri, Mar 7, 2014 at 11:53 AM, Dimat Levchenko  wrote:

> Hi,
>
> Did anyone thought of using gerrit (or something similar) to manage sources
> and contributions? Are there any restrictions about repositories or
> limitations?
>
> Thank you.
>

Re: Contributions

[Jake Farrell]

The Apache infrastructure team is made up of volunteers and some paid
consultants. Links are provided below about Apache infra and how to get
involved, we are always looking for good volunteers.

-Jake

http://apache.org/dev/#infrastructure
http://apache.org/dev/infra-volunteer.html




On Fri, Mar 7, 2014 at 12:10 PM, Dimat Levchenko  wrote:

> I see. Thank you. Is there any article about apache infrastructure, how it
> works, who maintains it? It's interesting to know what did you try for
> maintenance, how do you like it, and what do you think about it.
> 7 бер. 2014 19:01, користувач "Jake Farrell" 
> написав:
>
> > Hi Dimat
> > Apache Infrastructure currently does not have a Gerrit installation and
> > there are no immediate plans to use it. We have Reviewboard setup for
> > Apache Thrift, but do not utilize it in out typical workflows. Right now
> > the preferred approach is to attach patchs to tickets with in the ASF
> jira.
> >
> > http://thrift.apache.org/docs/HowToContribute/
> >
> > -Jake
> >
> >
> > On Fri, Mar 7, 2014 at 11:53 AM, Dimat Levchenko 
> wrote:
> >
> > > Hi,
> > >
> > > Did anyone thought of using gerrit (or something similar) to manage
> > sources
> > > and contributions? Are there any restrictions about repositories or
> > > limitations?
> > >
> > > Thank you.
> > >
> >
>

Re: reconsidering the Apache CMS...

[Jake Farrell]

Hey Joe
Thanks for reaching out, we chose to go with a site generator over the
Apache CMS due to it initially not meeting all of our needs. Our current
needs for the site are

- Markdown to html conversion
- Global variables/config usable throughout in a template based layout
- Syntax highlighting
- Easily include code snippets from our source code base
- Ability to locally test before committing

-Jake




On Sun, Mar 16, 2014 at 12:44 PM, Joe Schaefer wrote:

> As it so happens I am interested in working on supporting
> thrift's use case as a potential user of the Apache CMS.
> While the CMS works well for massive projects there are
> things it could do better at supporting for more moderate
> sized sites like thrift's.
>
> I'd therefore like to engage you folks in a brainstorming session
> about what sorts of features you want for your site and to find
> simple ways of supporting those features for you.
>
> Thanks.

Re: reconsidering the Apache CMS...

[Jake Farrell]

No objections from me

-Jake


On Mon, Mar 17, 2014 at 12:04 PM, Joe Schaefer wrote:

> Any objections to me making a copy of the site
> tree alongside it called cms-site?  I'd like to
> get cracking on knocking up the supporting perl
> for this so we can continue to brainstorm...
>
>
>
>
> > On Sunday, March 16, 2014 1:53 PM, Joe Schaefer 
> wrote:
> > > On Sunday, March 16, 2014 1:40 PM, Jake Farrell 
> > wrote:
> >
> > Hey Joe
> >> Thanks for reaching out, we chose to go with a site generator over the
> >> Apache CMS due to it initially not meeting all of our needs. Our current
> >> needs for the site are
> >>
> >> - Markdown to html conversion
> >
> >
> > That one's easy- its the default for the cms.
> >
> >
> >> - Global variables/config usable throughout in a template based layout
> >
> >
> > Easy too- just create a perl hash somewhere and make it available to
> your views.
> >  Code your views to pass that hash along to your templates and you are
> all set.
> >  Note if your hash contains objects you can make method calls on them in
> your
> > templates.  Note: while I wouldn't recommend this in general, for smaller
> > projects like thrift that prefer convenience over separation of concerns
> you can
> > have the django template engine do a pass over your markdown before
> passing it
> > along to your actual template page, just as is seemingly common to other
> popular
> > site generation software.
> >
> >
> >> - Syntax highlighting
> >
> >
> > Comes with python's markdown support, but some people prefer the look of
> > javascript highlighters.
> >
> >> - Easily include code snippets from our source code base
> >
> >
> > Statically I hope.  No idea how to pull snippets out of your git repo
> via the
> > cms.
> >
> >> - Ability to locally test before committing
> >
> >
> > Belt and suspenders with the cms- you can build your changes before
> committing
> > with the build scripts, browse your changes before committing via the cms
> > webgui, or simply commit your changes and view the staging site prior to
> live
> > publication (which is a separate step).
> >
> >
> >
> >>
> >> -Jake
> >>
> >>
> >>
> >>
> >>
> >> On Sun, Mar 16, 2014 at 12:44 PM, Joe Schaefer
> > wrote:
> >>
> >>>  As it so happens I am interested in working on supporting
> >>>  thrift's use case as a potential user of the Apache CMS.
> >>>  While the CMS works well for massive projects there are
> >>>  things it could do better at supporting for more moderate
> >>>  sized sites like thrift's.
> >>>
> >>>  I'd therefore like to engage you folks in a brainstorming session
> >>>  about what sorts of features you want for your site and to find
> >>>  simple ways of supporting those features for you.
> >>>
> >>>  Thanks.
> >>
> >>
> >>
> >
>

[Announcement] New Committer: Randy Abernethy

[Jake Farrell]

On behalf of the Apache Thrift PMC, I would like to welcome our newest
committer to the project:

  Randy Abernethy

He has been extremely active contributing quality patches to many of the
client
libraries as well as helping answer questions on the dev and user lists. It
is my
honor to welcome him as a committer.

Congratulations and thank you for your hard work

Jake Farrell
Apache Thrift PMC

Re: reconsidering the Apache CMS...

[Jake Farrell]

; >>>>>>>
> >>>>>>>>better...
> >>>>>>>>>>
> >>>>>>>>>> I've done two things to make
> > this work
> >>>  well-
> >>>>first I
> >>>>> made
> >>>>>>  the
> >>>>>>>>number of
> >>>>>>>>>> child processes "aka
> > runners"
> >>>  tunable on
> >>>>a
> >>>>>>  per-project
> >>>>>>>   basis,
> >>>>>>>>and since the
> >>>>>>>>>> sitemap is going to build every page
> > anyway as
> >>>  the
> >>>>> slowest
> >>>>>>  page to
> >>>>>>>
> >>>>>>>>build, I
> >>>>>>>>>> memoized the main view that builds
> > the
> >>>  markdown
> >>>>pages
> >>>>> for
> >>>>>>  thrift.
> >>>>>>>   The
> >>>>>>>>best
> >>>>>>>>>> results are when there's only
> > one runner
> >>>  so we
> >>>>get
> >>>>> the
> >>>>>>  full
> >>>>>>>   benefit
> >>>>>>>>of
> >>>>>>>>>> memoization: typical site build
> > times are
> >>>>consistently
> >>>>> under
> >>>>>>  2
> >>>>>>>   seconds
> >>>>>>>>now.
> >>>>>>>>>>
> >>>>>>>>>> You'll appreciate why I am such
> > a
> >>>  performance
> >>>>> stickler
> >>>>>>  for the
> >>>>>>>   CMS
> >>>>>>>>when
> >>>>>>>>>>     you start using the bookmarklet,
> > since builds
> >>>  are
> >>>>the
> >>>>> only
> >>>>>>>   asynchronous
> >>>>>>>>>> part of the process from making a
> > change to a
> >>>  page
> >>>>and
> >>>>>>  publishing
> >>>>>>>   the
> >>>>>>>>>> results.  Ideally when the system is
> > working
> >>>  well
> >>>>the
> >>>>> builds
> >>>>>>>   happen
> >>>>>>>>before
> >>>>>>>>>> you have time to go looking for
> > them, but you
> >>>  do
> >>>>need to
> >>>>> be
> >>>>>>>   mindful of
> >>>>>>>>not
> >>>>>>>>>> publishing before the built pages
> > have been
> >>>>committed
> >>>>> back to
> >>>>>>  svn
> >>>>>>>   by
> >>>>>>>>>> buildbot.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>> On Monday, March 17, 2014 11:59
> > PM, Joe
> >>>>Schaefer
> >>>>>>>>
> >>>>>>>>>> wrote:
> >>>>>>>>>>>> Ok there's enough of an
> > idea about
> >>>  how
> >>>>to
> >>>>> port
> >>>>>>  the
> >>>>>>>   rest of
> >>>>>>>>the site's
> >>>>>>>>>>> pages over based on the porting
> > work
> >>>  I've
> >>>>> already
> >>>>>>  done
> >>>>>>>   that
> >>>>>>>>it's time
> >>>>>>>>>>> for me to step back and let you
> > guys catch
> >>>  up.
&g

Re: reconsidering the Apache CMS...

[Jake Farrell]

Hey Joe
Thanks for making the additions to the Apache CMS to meet our use case. I'm
not seeing any blockers at the moment, lets cut over and we can fix any
edge cases if needed

-Jake



On Mon, Mar 24, 2014 at 1:39 PM, Joseph Schaefer wrote:

> Done.  Anything else we need to look at before going live?
>
> Sent from my iPhone
>
> > On Mar 23, 2014, at 3:53 PM, Roger Meier 
> wrote:
> >
> > any idea how to fix this URL:
> > http://thrift.staging.apache.org/test/ThriftTest.thrift
> > we need to keep the filename for working links within the
> > test/README.md file.
> >
> > What about a footer for docs genertated from source tree?
> > [snippet:path=test/README.md, footer=1]
> >
> > I added the following snippet to content/test/index.md:
> > ---SNIP---
> > This page was generated from Apache Thrift's **source tree docs**:
> > [test/README.md](
> https://git-wip-us.apache.org/repos/asf/thrift/repo?p=thrift.git;a=blob;f=test/ThriftTest.thrift;hb=HEAD
> )
> > ---SNIP---
> >
> > would be great to get this generated into the page via snippet.
> >
> > -roger
> >
> >
> >> On 23.03.2014 19:04, Joe Schaefer wrote:
> >> The CMS codebase as well as the thrift build system
> >> already supports it Roger, someone just needs to create
> >> the files in the content tree that point at the source
> >> files in the git repo.  If you want to script this process
> >> in scripting language du jour, go for it, but I cannot
> >> justify spending contractor time doing this work for the
> >> community's behalf as it is unlikely to be needed elsewhere.
> >> I would think you only need the script to run when some
> >> path to a README.md file changes in the thrift.git tree,
> >> so it doesn't need to be incorporated into each site build.
> >>
> >>
> >>
> >>>> On Sunday, March 23, 2014 9:15 AM, Roger Meier <
> ro...@bufferoverflow.ch> wrote:
> >>>> Hi
> >>>
> >>>> On 23.03.2014 03:19, Jake Farrell wrote:
> >>>>  Hey Joe
> >>>>  Reviewing the staging site it looks like its almost 99% there other
> than
> >>>>  some styling within the code snippets. I'm good if we want to cut
> over
> >>> to
> >>>>  using this and then work on the additional features that had been
> mentioned
> >>>>  afterwords. Any objections to cutting over?
> >>> I would really like to see this automatic README.md includes from
> source
> >>> tree, to have a real additional feature beside of what we already have
> >>> today.
> >>>
> >>> I'm absolutely with you.
> >>> Apache projects shall use other Apache projects whenever possible.
> >>>
> >>>>  On Sat, Mar 22, 2014 at 4:36 PM, Joe Schaefer
> >>> wrote:
> >>>>
> >>>>>  May I suggest a script that creates files in content/
> >>>>>  containing a single line
> >>>>>
> >>>>>  [snippet:path=...]
> >>> this sounds like a plan
> >>>
> >>>>>
> >>>>>  (with no 'lang' argument) that lets the CMS pull raw content
> >>> from
> >>>>>  thrift.git
> >>>>>  and add it directly to the built pages.  That way you only need to
> run
> >>> the
> >>>>>  script that generates these files when a path changes in your
> >>> thrift.git
> >>>>>  repo.
> >>> What I had in mind is a automatic search of README.md files across the
> >>> source tree and generate the site with these automatically.
> >>> Kind of a central controller that maps all the URL's.
> >>> no additional work when a new README.md file is added.
> >>> however, a script can do this as interim soultion.
> >>>>>
> >>>>>  You can commit directly to the cms svn tree or via the webgui which
> >>> does
> >>>>>  the same thing.
> >>> Great!
> >>>
> >>> What about local preview when doing perl modifications?
> >>>
> >>> -roger
> >>>
> >>>
> >>>>>
> >>>>>
> >>>>>>  On Saturday, March 22, 2014 4:20 PM, Roger Meier <
> >>>>>  ro...@bufferoverflow.ch> wrote:
> >>>>>>>  I still see some issues and still miss to feature mentioned.
> >>&

Re: Error while running nodejs test servers and clients

[Jake Farrell]

Run the following before npm install, I ran into this issue as well when
testing the vagrant image, I have a patch for it which I have not committed
yet

sudo npm config set registry http://registry.npmjs.org/

-Jake


On Thu, Mar 27, 2014 at 2:20 PM, Chamila Wijayarathna <
cdwijayarat...@gmail.com> wrote:

> Hello all,
> I trying to run sample nodejs severs and clients in lib/nodejs folder. But
> when I tried to run them I am getting following error.
>
> *chamila@chamila-Dell-System-Vostro-3450:~/GSoC/thrift$ nodejs
> lib/nodejs/test/client.js -p binary -t buffered *
>
> *module.js:337*
> *throw new Error("Cannot find module '" + request + "'");*
> *  ^*
> *Error: Cannot find module 'thrift/transport'*
> *at Function._resolveFilename (module.js:337:11)*
> *at Function._load (module.js:279:25)*
> *at Module.require (module.js:359:17)*
> *at require (module.js:375:17)*
> *at Object.
> (/home/chamila/GSoC/thrift/lib/nodejs/test/client.js:27:24)*
> *at Module._compile (module.js:446:26)*
> *at Object..js (module.js:464:10)*
> *at Module.load (module.js:353:32)*
> *at Function._load (module.js:311:12)*
> *at Array.0 (module.js:484:10)*
>
> I tried to install thrift/transport using npm, but it didn't work either.
>
> *chamila@chamila-Dell-System-Vostro-3450:~/GSoC/thrift$ sudo npm install
> thrift/transport*
> *[sudo] password for chamila: *
> *npm ERR! Could not install: thrift/transport*
>
> *npm ERR! Error: ENOENT, stat 'thrift/transport'*
> *npm ERR! You may report this log at:*
> *npm ERR! >*
> *npm ERR! or use*
> *npm ERR! reportbug --attach /home/chamila/GSoC/thrift/npm-debug.log
> npm*
> *npm ERR! *
> *npm ERR! System Linux 3.8.0-19-generic*
> *npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
> "thrift/transport"*
> *npm ERR! cwd /home/chamila/GSoC/thrift*
> *npm ERR! node -v v0.6.19*
> *npm ERR! npm -v 1.1.4*
> *npm ERR! path thrift/transport*
> *npm ERR! code ENOENT*
> *npm ERR! message ENOENT, stat 'thrift/transport'*
> *npm ERR! errno {}*
> *npm ERR! *
> *npm ERR! Additional logging details can be found in:*
> *npm ERR! /home/chamila/GSoC/thrift/npm-debug.log*
> *npm not ok*
>
> What should I do for this?
>
>
> --
> *Chamila Dilshan Wijayarathna,*
> SMIEEE, SMIESL,
> Undergraduate,
> Department of Computer Science and Engineering,
> University of Moratuwa.
>

Updated contributor how to guide

[Jake Farrell]

I've updated the contributor guide for recent changes we have been making
on the infra side which will now enable us to accept pull requests from
GitHub.

http://thrift.apache.org/docs/HowToContribute

Comitters, I have also added a new page detailing the necessary steps for
dealing with a GitHub pull request. Before accepting/merging the pull
request please ensure that the automated email from GitHub about the pull
request has reached the dev@ list.

http://thrift.apache.org/docs/committers/HowToCommit

If anyone has any questions please let me know
-Jake

Re: [DISCUSS] release process for package/dependency managers which require config files in the repo root

[Jake Farrell]

I would like to avoid the situation where we have a separate repo for each
client lib which would make building, cross testing and maintaining
extremely difficult. As long as it clear in a README included in these
repositories that they are not for development and are only for released
versions then this sounds like a reasonable approach.

-Jake


On Fri, Apr 4, 2014 at 11:46 AM, Randy Abernethy
wrote:

> Hey All,
>
> Sounds like we have a workable compromise which will make thrift easy to
> install in PHP and JavaScript and keep the thrift master root clean. The
> fact that composer.json and bower.json need to be in the repo root has
> inspired the creation of thrift-php and thrift-js repos for releases. Each
> of these repos will be updated with every thrift release allowing any
> version up to the current release to be installed.
>
> Let me know if the process and code below sounds right to everyone (this
> is the PHP example but you can extrapolate the JS process):
>
> *When 0.9.2 is released we will:*
> {code}
> 1. git clone thrift-php
> 2. cd thrift-php
> 3. cp ../thrift/lib/php/{*, composer.json} .
> 4. git add -A
> 5. git commit -m "thrift-0.9.2"
> {code}
>
> All of the PHP eco system installers and dependency managers will point to:
> https://github.com/apache/thrift-php
>
> The composer.json will be checked in to the master in thrift/lib/php. The
> composer.json contents will need to be relative to / so that it works when
> copied to thrift-php. The following is the proposed composer.json contents:
>
> {code}
> {
> "name": "apache/thrift",
> "description": "Apache Thrift RPC system",
> "homepage": "http://thrift.apache.org/";,
> "type": "library",
> "license": "Apache-2.0",
> "authors": [
> {
> "name": "Apache Thrift Developers",
> "email": "dev@thrift.apache.org",
> "homepage": "http://thrift.apache.org";
> }
> ],
> "support": {
> "email": "dev@thrift.apache.org",
> "issues": "https://issues.apache.org/jira/browse/THRIFT";
> },
> "require": {
> "php": ">=5.3.0"
> },
> "autoload": {
> "psr-0": {"Thrift": "src/"}
> },
> "target-dir": ".",
> "minimum-stability": "dev",
> "extra": {
> "branch-alias": {
> "dev-master": "0.9.x-dev"
> }
> }
> }
> {code}
>
> Please comment if you see problems with this process! See THRIFT-1743 for
> more discussion.
>
> Thanks,
> Randy
>

Re: Re: [DISCUSS] release process for package/dependency managers which require config files in the repo root

[Jake Farrell]

If the files are in the root level then both bower and php will always use
the trunk version and not the given released version. I really do not like
how both of these packaged systems behave and do not consider for anything
outside of just a repo with php or js code. Also the js code in its current
form does not contain the actual packaged source that would be needed by
the bower file (the generated dist/* files).

We can avoid pull requests to these repositories by not enabling the
mirroring of them at github. Another option that might be a lot easier
looking at the internals of both could be from out svn dist repo, something
like

https://dist.apache.org/repos/dist/release/thrift/x.x.x/lib/php/composer.json
https://dist.apache.org/repos/dist/release/thrift/x.x.x/lib/js/bower.json

This would allow us to keep them per release and also not enable pull
requests and does not open up another repository that needs to be
maintained, just a package step when deploying the given release. I'll look
into this further and see if dist.a.o has any requirements such as only tar
packages or not due to mirrors

-Jake


On Fri, Apr 4, 2014 at 8:03 PM, Roger Meier  wrote:

> I agree with Jake, splitting up will make it more difficult to mange and
> ensure cross language interoperability.
> It's hard enough to manage the codebase and push things forward.
>
> I think we should not add additional repos.
> Get additional pull requests for other repos?
> How to handle all of this?
> How to explain to the users?
>
> Just put bower.json and composer.json within root folder to simplify
> shipment of these libs.
> Mission complete!
>
> -roger
>
> Quoting Jake Farrell :
>
>  I would like to avoid the situation where we have a separate repo for each
>> client lib which would make building, cross testing and maintaining
>> extremely difficult. As long as it clear in a README included in these
>> repositories that they are not for development and are only for released
>> versions then this sounds like a reasonable approach.
>>
>> -Jake
>>
>>
>> On Fri, Apr 4, 2014 at 11:46 AM, Randy Abernethy
>> wrote:
>>
>>  Hey All,
>>>
>>> Sounds like we have a workable compromise which will make thrift easy to
>>> install in PHP and JavaScript and keep the thrift master root clean. The
>>> fact that composer.json and bower.json need to be in the repo root has
>>> inspired the creation of thrift-php and thrift-js repos for releases.
>>> Each
>>> of these repos will be updated with every thrift release allowing any
>>> version up to the current release to be installed.
>>>
>>> Let me know if the process and code below sounds right to everyone (this
>>> is the PHP example but you can extrapolate the JS process):
>>>
>>> *When 0.9.2 is released we will:*
>>> {code}
>>> 1. git clone thrift-php
>>> 2. cd thrift-php
>>> 3. cp ../thrift/lib/php/{*, composer.json} .
>>> 4. git add -A
>>> 5. git commit -m "thrift-0.9.2"
>>> {code}
>>>
>>> All of the PHP eco system installers and dependency managers will point
>>> to:
>>> https://github.com/apache/thrift-php
>>>
>>> The composer.json will be checked in to the master in thrift/lib/php. The
>>> composer.json contents will need to be relative to / so that it works
>>> when
>>> copied to thrift-php. The following is the proposed composer.json
>>> contents:
>>>
>>> {code}
>>> {
>>> "name": "apache/thrift",
>>> "description": "Apache Thrift RPC system",
>>> "homepage": "http://thrift.apache.org/";,
>>> "type": "library",
>>> "license": "Apache-2.0",
>>> "authors": [
>>> {
>>> "name": "Apache Thrift Developers",
>>> "email": "dev@thrift.apache.org",
>>> "homepage": "http://thrift.apache.org";
>>> }
>>> ],
>>> "support": {
>>> "email": "dev@thrift.apache.org",
>>> "issues": "https://issues.apache.org/jira/browse/THRIFT";
>>> },
>>> "require": {
>>> "php": ">=5.3.0"
>>> },
>>> "autoload": {
>>> "psr-0": {"Thrift": "src/"}
>>> },
>>> "target-dir": ".",
>>> "minimum-stability": "dev",
>>> "extra": {
>>> "branch-alias": {
>>> "dev-master": "0.9.x-dev"
>>> }
>>> }
>>> }
>>> {code}
>>>
>>> Please comment if you see problems with this process! See THRIFT-1743 for
>>> more discussion.
>>>
>>> Thanks,
>>> Randy
>>>
>>>
>
>

Re: [DISCUSS] contribution and commit messages

[Jake Farrell]

Hey Roger
I'm in favor of keeping things as simple for the committer as possibly,
introducing more steps or flags just leave the possibility for something to
get missed.


1. Done, see doc/contributing.md and doc/committers.md

2. The author field is what we currently use for who has {tested, reviewed,
committed} a given patch, I do not think we need to introduce more flags
that could be forgotten when submitting a contribution. Along those lines,
I think that what your had as the commit message for the lua contribution
was exactly what we need (having the client in commit messages is redundant
as our changelog is made up from the jira tickets and those *should* all
include a component and fix version)

3. Patches are not included with the github pull request email
notifications and it is not planned to add them. (We (infra hat on now) had
discussions when working on the pull request notifications and decided to
not include them intentionally).

4.  format-patch is the compliment to git-am, using the unified diff should
be fine for our needs. git show HEAD > thrift-xxx.patch matches what github
is giving us with the .patch.

-Jake



On Fri, Apr 4, 2014 at 8:34 PM, Roger Meier  wrote:

> All,
>
> We had several discussion about commit messages on multiple channels.
> Let's discuss this here on the dev list.
>
> Question 1: Documentation
> merge HowToCommit + HowToContribute into /CONTRIBUTE.md
> and include it easily with our brand new Apache CMS on the web site?
>
> Question 2: Developer's Certificate of Origin
> Today we have this commit style:
> --- http://thrift.apache.org/docs/committers/HowToCommit ---
> THRIFT-###:
> Client: 
> Patch: 
>
> Description of what was fixed or addressed.
>
> <%
> if this is a github pull request then copy the below block
> from the GitHub email that came to dev@ list, this will
> automatically close the GitHub pull request
> %>
> Github Pull Request: This closes #XX
> --- http://thrift.apache.org/docs/committers/HowToCommit ---
> Hmm, I did something wrong on the Lua commit...sorry!
>
> What do you think about git best practice known from other projects to get
> *Developer's Certificate of Origin*, such as here:
> - https://www.kernel.org/doc/Documentation/SubmittingPatches
> - http://www.denx.de/wiki/U-Boot/Patches
>
> e.g. *git commit -s* automatically adds a Signed-off-by line to the commit
> message.
> Signed-off-by: Patch Creator 
>
> beside of the Signed-off-by tag the following are well known:
> Tested-by: Tester 
> Reviewed-by: Reviewer 
> Suggested-by: Idea Creator 
> Acked-by: Component Maintainer 
>
>
> Question 3: git am
> Would it make sense to start using this?
>
> Question 4: patch creation
> What about that workflow:
> git clone https://git-wip-us.apache.org/repos/asf/thrift.git thrift
> cd thrift
> git pull origin master
> # create a local feature branch
> git checkout -b THRIFT-1681
> # make the changes and commit to your local feature branch
> git commit -a
> # format patch
> git format-patch -1
> # submit the patch or create a pull request
>
>
> all the best!
> roger
> ;-r
>

Re: THRIFT-2433 - Manual control of OpenSSL initialization

[Jake Farrell]

Hey Alan
Thanks for the patch, appreciate the help here. the Fix Version and Patch
Available flags on the ticket where not set. These fields help us sort out
reviewable tickets over the feature requests and backlog. I've updated the
ticket and someone will review it shortly

-Jake




On Sun, Apr 13, 2014 at 11:27 AM, Alan Dunn  wrote:

> Hi folks,
>
> I submitted issue 2433
> (https://issues.apache.org/jira/browse/THRIFT-2433) about two weeks
> ago to allow users to take manual control over OpenSSL initialization
> rather than having Thrift's TSSLSocket do it because Thrift's
> automatic control doesn't play nicely with other libraries and can
> lead to OpenSSL deinitialization in unexpected places.  Since a little
> while went by, and this was the first patch I've submitted to Thrift,
> I figured I might ask on the dev list whether I did something wrong
> that's causing the patch to be ignored, or whether it's some
> combination of not high enough priority/you folks are too busy (which
> I would completely understand).
>
> Thanks,
> - Alan
>

Re: thrift docs

[Jake Farrell]

Hi Asternie
The hbase idl is really well commented [1] with getRowTs defined as follows

-Jake

 /**
   * Get all the data for the specified table and row at the specified
   * timestamp. Returns an empty list if the row does not exist.
   *
   * @return TRowResult containing the row and map of columns to TCells
   */
  list getRowTs(
/** name of the table */
1:Text tableName,

/** row key */
2:Text row,

/** timestamp */
3:i64 timestamp,

/** Get attributes */
4:map attributes
  ) throws (1:IOError io)


[1]: 
http://svn.apache.org/repos/asf/hbase/trunk/hbase-thrift/src/main/resources/org/apache/hadoop/hbase/thrift/Hbase.thrift



On Wed, Apr 16, 2014 at 10:24 AM, Asternie Rasenburg wrote:

> Where can I find detailed descriptions for the functions,
> with arguments and what it does?
>
> I'm searching now for the meaning of  getRowTs.
> I can only find the types of arguments.
> I'm missing detailed function description.
>

Re: [jira] [Commented] (THRIFT-2571) Simplify cross compilation using CMake

[Jake Farrell]

+1 to pushing this to post 0.9.2 and we circle back and look at it then

-Jake


On Tue, Jun 17, 2014 at 9:42 AM, Henrique Mendonça 
wrote:

> Hi guys,
>
> So just to clarify, what do you think about replacing the
> "contrib/mingw-cross-compile.sh" by the cmake cross compilation in the
> documentation like Roger suggested in the ticket?
> Anyone against it? Then do we delete the script to avoid redundancy or
> leave it?
> I'm also ok to first release 0.9.2 and leave it for 1.0
>
> To summarise: it's much faster to build, doesn't require reconfiguring the
> file tree and can be built out-of-source without touching the file tree at
> all. It obviously adds an extra dependency to the cross-platform build
> [only] but it's already pre-installed in most platforms or it's very easy
> to do so.
>
> Cheers,
> Henrique
>
>
>
> On 17 June 2014 13:40, Hudson (JIRA)  wrote:
>
> >
> > [
> >
> https://issues.apache.org/jira/browse/THRIFT-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033691#comment-14033691
> > ]
> >
> > Hudson commented on THRIFT-2571:
> > 
> >
> > SUCCESS: Integrated in Thrift #1185 (See [
> > https://builds.apache.org/job/Thrift/1185/])
> > THRIFT-2571 doc and speed up travis build (henrique: rev
> > 55087a49d335db7da23e23d8d8a9368e4e5ae7a6)
> > * compiler/cpp/README.md
> > * .travis.yml
> >
> >
> > > Simplify cross compilation using CMake
> > > --
> > >
> > > Key: THRIFT-2571
> > > URL: https://issues.apache.org/jira/browse/THRIFT-2571
> > > Project: Thrift
> > >  Issue Type: Improvement
> > >  Components: Compiler (General)
> > >Affects Versions: 1.0
> > >Reporter: Pascal Bach
> > >Assignee: Henrique Mendonça
> > >Priority: Minor
> > >
> > > Using CMake would simplify cross compilation.
> > > The for example the same build script can be used to build:
> > > - Native for Linux using GCC
> > > - Native for Windows using Visual Studio
> > > - Cross compile for ARM on Linux
> > > - Cross compile for Windows form Linux using mingw32
> > > It also makes it easy to generate project files for Eclipse or Visual
> > Studio.
> > > h2. Some examples:
> > > {code:title=Create an eclipse project|borderStyle=solid}
> > > mkdir build_ec && cd build_ec
> > > cmake -G "Eclipse CDT4 - Unix Makefiles" ../compiler/cpp
> > > make
> > > {code}
> > > Now open the folder build_ec using eclipse.
> > > {code:title=Create a Visual Studio project (Windows
> > only)|borderStyle=solid}
> > > mkdir build_vs && cd build_vs
> > > cmake -G "Visual Studio 12" ../compiler/cpp
> > > {code}
> > > Now open the folder build_vs using Visual Studio.
> > > {code:title=Cross compile using mingw32|borderStyle=solid}
> > > mkdir build_mingw32 && cd build_mingw32
> > > cmake -DCMAKE_TOOLCHAIN_FILE=../contrib/mingw32-toolchain.cmake
> > ../compiler/cpp
> > > make
> > > {code}
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v6.2#6252)
> >
>