[RESULT][VOTE] Apache Accumulo 1.9.3-rc1
This vote was superseded by the vote for RC2. On Wed, Mar 27, 2019 at 10:45 AM Keith Turner wrote: > > On Wed, Mar 27, 2019 at 1:09 AM Christopher wrote: > > > > I'll also -1 for this. I'll put together an RC2 with the fix. > > Thanks Christopher. I successfully ran mvn verify with the #1057 patch. > > > > > On Tue, Mar 26, 2019 at 2:05 PM Mike Miller wrote: > > > > > > -1 So we can get a fix for this > > > > > > On Tue, Mar 26, 2019 at 1:38 PM Keith Turner wrote: > > > > > > > -1 > > > > > > > > https://github.com/apache/accumulo/pull/1057 > > > > > > > > On Mon, Mar 25, 2019 at 7:41 PM Christopher wrote: > > > > > > > > > > Accumulo Developers, > > > > > > > > > > Please consider the following candidate for Apache Accumulo 1.9.3. > > > > > > > > > > Git Commit: > > > > > d35a3f1e2be56779cf8b839a56988fdfcb34f600 > > > > > Branch: > > > > > 1.9.3-rc1 > > > > > > > > > > If this vote passes, a gpg-signed tag will be created using: > > > > > git tag -f -m 'Apache Accumulo 1.9.3' -s rel/1.9.3 \ > > > > > d35a3f1e2be56779cf8b839a56988fdfcb34f600 > > > > > > > > > > Staging repo: > > > > https://repository.apache.org/content/repositories/orgapacheaccumulo-1076 > > > > > Source (official release artifact): > > > > > > > > > https://repository.apache.org/content/repositories/orgapacheaccumulo-1076/org/apache/accumulo/accumulo/1.9.3/accumulo-1.9.3-src.tar.gz > > > > > Binary: > > > > https://repository.apache.org/content/repositories/orgapacheaccumulo-1076/org/apache/accumulo/accumulo/1.9.3/accumulo-1.9.3-bin.tar.gz > > > > > (Append ".sha1", ".md5", or ".asc" to download the signature/hash for > > > > > a given artifact.) > > > > > > > > > > In addition to the tarballs, and their signatures, the following > > > > > checksum > > > > > files will be added to the dist/release SVN area after release: > > > > > accumulo-1.9.3-src.tar.gz.sha512 will contain: > > > > > SHA512 (accumulo-1.9.3-src.tar.gz) = > > > > > > > > > f9adb1c3ace6326cc93240addb925d6b9f66636c0f5a204727d20eab6a3f14d7e838898fa6fb77e165013684757598266440630daa10be293d2d71cc528963d4 > > > > > accumulo-1.9.3-bin.tar.gz.sha512 will contain: > > > > > SHA512 (accumulo-1.9.3-bin.tar.gz) = > > > > > > > > > f52d0fb86b64bd6787812b0645e39fe36ff6a96322b2daf12d160279fca7a3ea08127d78b988e57e8732bf34f7e76a0da7123896d132b0a7a1bba6dbf6ed0d11 > > > > > > > > > > Signing keys are available at > > > > > https://www.apache.org/dist/accumulo/KEYS > > > > > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D) > > > > > > > > > > Release notes (in progress) can be found at: > > > > > https://accumulo.apache.org/release/accumulo-1.9.3/ > > > > > > > > > > Release testing instructions: > > > > > https://accumulo.apache.org/contributor/verifying-release > > > > > > > > > > Please vote one of: > > > > > [ ] +1 - I have verified and accept... > > > > > [ ] +0 - I have reservations, but not strong enough to vote against... > > > > > [ ] -1 - Because..., I do not accept... > > > > > ... these artifacts as the 1.9.3 release of Apache Accumulo. > > > > > > > > > > This vote will remain open until at least Fri Mar 29 00:00:00 UTC > > > > > 2019. > > > > > (Thu Mar 28 20:00:00 EDT 2019 / Thu Mar 28 17:00:00 PDT 2019) > > > > > Voting can continue after this deadline until the release manager > > > > > sends an email ending the vote. > > > > > > > > > > Thanks! > > > > > > > > > > P.S. Hint: download the whole staging repo with > > > > > wget -erobots=off -r -l inf -np -nH \ > > > > > > > > > https://repository.apache.org/content/repositories/orgapacheaccumulo-1076/ > > > > > # note the trailing slash is needed > > > >
Re: [VOTE] Apache Accumulo 1.9.3-rc2
On Fri, Mar 29, 2019 at 1:42 PM Keith Turner wrote: > > On Thu, Mar 28, 2019 at 8:57 PM Christopher wrote: > > > > -1 due to https://github.com/apache/accumulo/issues/1064 > > Do you know if this is a new bug since 1.9.2? Or does the same > problem exist in 1.9.2, 1.9.1, etc? > The underlying issues with the quality of the native code (assumptions about undefined behavior in the STL vector implementation) exists in those versions, but I'm extra concerned because #767 is new to 1.9.3, and this new issue lowers my confidence in the fix for #767 being a good one.
Re: [VOTE] Apache Accumulo 1.9.3-rc2
-1 I ran into the following issue when trying to verify continuous ingest. https://github.com/apache/accumulo/issues/1065 On Wed, Mar 27, 2019 at 7:57 PM Christopher wrote: > > Accumulo Developers, > > Please consider the following candidate for Apache Accumulo 1.9.3. > > This supersedes RC1 and contains the following change: > https://github.com/apache/accumulo/pull/1057 > > Git Commit: > 94f9782242a1f336e176c282f0f90063a21e361d > Branch: > 1.9.3-rc2 > > If this vote passes, a gpg-signed tag will be created using: > git tag -f -m 'Apache Accumulo 1.9.3' -s rel/1.9.3 \ > 94f9782242a1f336e176c282f0f90063a21e361d > > Staging repo: > https://repository.apache.org/content/repositories/orgapacheaccumulo-1077 > Source (official release artifact): > https://repository.apache.org/content/repositories/orgapacheaccumulo-1077/org/apache/accumulo/accumulo/1.9.3/accumulo-1.9.3-src.tar.gz > Binary: > https://repository.apache.org/content/repositories/orgapacheaccumulo-1077/org/apache/accumulo/accumulo/1.9.3/accumulo-1.9.3-bin.tar.gz > (Append ".sha1", ".md5", or ".asc" to download the signature/hash for > a given artifact.) > > In addition to the tarballs, and their signatures, the following checksum > files will be added to the dist/release SVN area after release: > accumulo-1.9.3-src.tar.gz.sha512 will contain: > SHA512 (accumulo-1.9.3-src.tar.gz) = > b366b89295b1835038cb242f8ad46b1d8455753a987333f0e15e3d89749540f2cd59db1bc6cf7100fc9050d3d0bc7340a3b661381549d40f2f0223d4120fd809 > accumulo-1.9.3-bin.tar.gz.sha512 will contain: > SHA512 (accumulo-1.9.3-bin.tar.gz) = > cc909296d9bbd12e08064fccaf21e81b754c183a8264dfa2575762c76705fd0c580b50c2b224c60feaeec120bd618fba4d6176d0f53e96e1ca9da0d9e2556f1f > > Signing keys are available at https://www.apache.org/dist/accumulo/KEYS > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D) > > Release notes (in progress) can be found at: > https://accumulo.apache.org/release/accumulo-1.9.3/ > > Release testing instructions: > https://accumulo.apache.org/contributor/verifying-release > > Please vote one of: > [ ] +1 - I have verified and accept... > [ ] +0 - I have reservations, but not strong enough to vote against... > [ ] -1 - Because..., I do not accept... > ... these artifacts as the 1.9.3 release of Apache Accumulo. > > This vote will remain open until at least Sun Mar 31 00:00:00 UTC 2019. > (Sat Mar 30 20:00:00 EDT 2019 / Sat Mar 30 17:00:00 PDT 2019) > Voting can continue after this deadline until the release manager > sends an email ending the vote. > > Thanks! > > P.S. Hint: download the whole staging repo with > wget -erobots=off -r -l inf -np -nH \ > https://repository.apache.org/content/repositories/orgapacheaccumulo-1077/ > # note the trailing slash is needed
Re: Combining output of multiple filters/iterators
You cannot feasibly hold onto some intermediate batch of nodes in memory. You're invalidating the general premise of how Accumulo iterators are meant to work in doing this. Further, an Iterator can _only_ safely operate within one row of a table. Two adjacent rows may be located on two different physical machines. Would suggest you read through this presentation and try to take some time to understand why they did it this way: http://www.pdl.cmu.edu/SDI/2013/slides/big_graph_nsa_rd_2013_56002v1.pdf. You might also be able to take something from Shana Hutchison's work on Graphulo: https://arxiv.org/abs/1606.07085 On 3/29/19 2:20 PM, Enas Alkawasmi wrote: Thank you for this suggestion. i have one question, c I pass options to the new source that are from the result of the current iterator? . the new iterator need to get the parent nodes from the the current one how can enforce the iterator to wait for the result form its preceding iterator? -- Sent from: http://apache-accumulo.1065345.n5.nabble.com/Developers-f3.html
Re: Combining output of multiple filters/iterators
Thank you for this suggestion. i have one question, c I pass options to the new source that are from the result of the current iterator? . the new iterator need to get the parent nodes from the the current one how can enforce the iterator to wait for the result form its preceding iterator? -- Sent from: http://apache-accumulo.1065345.n5.nabble.com/Developers-f3.html
Re: [VOTE] Apache Accumulo 1.9.3-rc2
On Thu, Mar 28, 2019 at 8:57 PM Christopher wrote: > > -1 due to https://github.com/apache/accumulo/issues/1064 Do you know if this is a new bug since 1.9.2? Or does the same problem exist in 1.9.2, 1.9.1, etc? > > On Thu, Mar 28, 2019 at 6:34 PM Mike Miller wrote: > > > > -0 > > Successfully verified the hashes and signatures for the src and binary > > tarballs. > > Successfully built from the source tarball. > > I have concerns over native map compatibility between versions of the gcc > > compiler on Fedora. Not enough to stop the release, since there is a work > > around and seems specific to only Fedora. > > I was not able to get NativeMapIT to pass in my environment. > > > > On Thu, Mar 28, 2019 at 6:20 PM Mike Miller wrote: > > > > > I did "sudo dnf downgrade gcc-c++" on Fedora 28, which it took me all the > > > way back to 8.0.1 and it still crashes. So it only works on 8.2.1? > > > > > > On Thu, Mar 28, 2019 at 5:59 PM Christopher wrote: > > > > > >> This problem appears to be introduced with gcc-c++ 8.3(.1?). When I do > > >> `sudo dnf downgrade gcc-c++` back to 8.2.1, it works fine. > > >> > > >> On Thu, Mar 28, 2019 at 3:01 PM Mike Miller wrote: > > >> > > > >> > I am seeing a crash in NativeMapIT running on my Fedora 28 VM using > > >> Oracle jdk1.8.0_161: > > >> > [INFO] Running org.apache.accumulo.test.functional.NativeMapIT > > >> > [WARNING] Corrupted STDOUT by directly writing to native stream in > > >> forked JVM 1. See FAQ web page and the dump file > > >> /home/mike/Downloads/accumulo-1.9.3/test/target/failsafe-reports/2019-03-28T14-09-45_055-jvmRun1.dumpstream > > >> > > > >> > I have attached the stacktrace. > > >> > > > >> > On Wed, Mar 27, 2019 at 7:57 PM Christopher > > >> wrote: > > >> >> > > >> >> Accumulo Developers, > > >> >> > > >> >> Please consider the following candidate for Apache Accumulo 1.9.3. > > >> >> > > >> >> This supersedes RC1 and contains the following change: > > >> >> https://github.com/apache/accumulo/pull/1057 > > >> >> > > >> >> Git Commit: > > >> >> 94f9782242a1f336e176c282f0f90063a21e361d > > >> >> Branch: > > >> >> 1.9.3-rc2 > > >> >> > > >> >> If this vote passes, a gpg-signed tag will be created using: > > >> >> git tag -f -m 'Apache Accumulo 1.9.3' -s rel/1.9.3 \ > > >> >> 94f9782242a1f336e176c282f0f90063a21e361d > > >> >> > > >> >> Staging repo: > > >> https://repository.apache.org/content/repositories/orgapacheaccumulo-1077 > > >> >> Source (official release artifact): > > >> >> > > >> https://repository.apache.org/content/repositories/orgapacheaccumulo-1077/org/apache/accumulo/accumulo/1.9.3/accumulo-1.9.3-src.tar.gz > > >> >> Binary: > > >> https://repository.apache.org/content/repositories/orgapacheaccumulo-1077/org/apache/accumulo/accumulo/1.9.3/accumulo-1.9.3-bin.tar.gz > > >> >> (Append ".sha1", ".md5", or ".asc" to download the signature/hash for > > >> >> a given artifact.) > > >> >> > > >> >> In addition to the tarballs, and their signatures, the following > > >> checksum > > >> >> files will be added to the dist/release SVN area after release: > > >> >> accumulo-1.9.3-src.tar.gz.sha512 will contain: > > >> >> SHA512 (accumulo-1.9.3-src.tar.gz) = > > >> >> > > >> b366b89295b1835038cb242f8ad46b1d8455753a987333f0e15e3d89749540f2cd59db1bc6cf7100fc9050d3d0bc7340a3b661381549d40f2f0223d4120fd809 > > >> >> accumulo-1.9.3-bin.tar.gz.sha512 will contain: > > >> >> SHA512 (accumulo-1.9.3-bin.tar.gz) = > > >> >> > > >> cc909296d9bbd12e08064fccaf21e81b754c183a8264dfa2575762c76705fd0c580b50c2b224c60feaeec120bd618fba4d6176d0f53e96e1ca9da0d9e2556f1f > > >> >> > > >> >> Signing keys are available at > > >> https://www.apache.org/dist/accumulo/KEYS > > >> >> (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D) > > >> >> > > >> >> Release notes (in progress) can be found at: > > >> >> https://accumulo.apache.org/release/accumulo-1.9.3/ > > >> >> > > >> >> Release testing instructions: > > >> >> https://accumulo.apache.org/contributor/verifying-release > > >> >> > > >> >> Please vote one of: > > >> >> [ ] +1 - I have verified and accept... > > >> >> [ ] +0 - I have reservations, but not strong enough to vote against... > > >> >> [ ] -1 - Because..., I do not accept... > > >> >> ... these artifacts as the 1.9.3 release of Apache Accumulo. > > >> >> > > >> >> This vote will remain open until at least Sun Mar 31 00:00:00 UTC > > >> >> 2019. > > >> >> (Sat Mar 30 20:00:00 EDT 2019 / Sat Mar 30 17:00:00 PDT 2019) > > >> >> Voting can continue after this deadline until the release manager > > >> >> sends an email ending the vote. > > >> >> > > >> >> Thanks! > > >> >> > > >> >> P.S. Hint: download the whole staging repo with > > >> >> wget -erobots=off -r -l inf -np -nH \ > > >> >> > > >> https://repository.apache.org/content/repositories/orgapacheaccumulo-1077/ > > >> >> # note the trailing slash is needed > > >> > > >
Re: Combining output of multiple filters/iterators
You may be able to use the deepCopy() method. This allows an iterator to create multiple copies of its source. Then it can seek each copy separately. Deep copies should be created in the init method. The following is an example of this. https://github.com/apache/accumulo/blob/rel/1.9.2/core/src/main/java/org/apache/accumulo/core/iterators/user/IntersectingIterator.java#L502 On Thu, Mar 28, 2019 at 9:44 AM Enas Alkawasmi wrote: > > I have the following problem model: > I have a graph stored in accumulo and I want to design iterators that > retrieve all nodes siblings of a given node. > I am thinking of a nested iterators(filters) that filter out the graph table > based on the node_ID and then each filter pass the resulted nodes to the > iterator comes after it as condition. I need to accumulate all the extracted > nodes and return them back to the client. I mean I need to have all the > processing to be done on the server side. My question is: how can make one > filter gets its options from the iterator executed before it. Also I want > each filter to be applied on the same original data-set but the outputs of > the iterators united after they all done. In other words I need the > iterators to call each others in nested way and they pass options from their > initial output to be used in the next iterator process but the result of > each iterator I need to keep it a side without affecting the original table > then I combine them at the end. > I read thoroughly in the map reduce examples with no luck. and I also read > about iterators and filers and I came to know that i cannot directly control > their execution but I can use priorities to control them. I still have the > challenge of interdependence between options. I need help in coding that in > java if some one can guide me to achieve what mentioned here: > " So it means if I set an Iterator and creates a buffer in memory with in > the iterator it will be created on each tablet server, right? This is the > map like function but how can I return and combine all the buffers client > side (the reduce)? Does Iterator has some functionality to make this process > easy? Further it would be a great help if you can provide some sample code > for the same or you have some similar implementation using iterators or > MapReduce" > I quoted from: > https://blogs.apache.org/accumulo/entry/thinking_about_reads_over_accumulo > > > > -- > Sent from: http://apache-accumulo.1065345.n5.nabble.com/Developers-f3.html
Re: Combining output of multiple filters/iterators
What do you mean by Christopher Tubbs-2 wrote > single iterator as a composition > of other, smaller components. what type of components are those? can you provide template code structure that I can follow in my code?. Do you think mapreduce can fit to my problem? -- Sent from: http://apache-accumulo.1065345.n5.nabble.com/Developers-f3.html
