| 2a99d97 | Pavel Yaskevich | 13 January 2015, 06:12:27 UTC | (Solr) only add + when AND query has more than one condition | 13 January 2015, 06:12:27 UTC |
| 9d650c3 | Dan LaRocque | 09 January 2015, 02:54:44 UTC | Add 0.5.3 to compat manifest | 10 January 2015, 00:21:14 UTC |
| e099458 | Dan LaRocque | 09 January 2015, 02:54:44 UTC | [maven-release-plugin] prepare for next development iteration | 10 January 2015, 00:21:14 UTC |
| 4fad7ce | Dan LaRocque | 09 January 2015, 02:54:43 UTC | [maven-release-plugin] prepare release 0.5.3 | 10 January 2015, 00:21:14 UTC |
| e3f9ce7 | Dan LaRocque | 09 January 2015, 02:53:37 UTC | Updating titan.compatible.versions prop | 10 January 2015, 00:21:14 UTC |
| 6cc7081 | Dan LaRocque | 09 January 2015, 02:52:17 UTC | Updating READMEish files for 0.5.3 | 10 January 2015, 00:21:09 UTC |
| 190d42c | Dan LaRocque | 08 January 2015, 23:07:35 UTC | Changing query fit expectations in tests e538117710d373b4b8690f4c0a32f40206f41890 changed some queries that used to be fitted into unfitted queries. This caused failures in test expectations around fitted-ness. This commit changes several fitted=true expectations to fitted=false in an attempt to match the new implementation behavior. | 08 January 2015, 23:09:15 UTC |
| e538117 | Matthias Broecheler | 08 January 2015, 20:29:09 UTC | Fixes #890 | 08 January 2015, 20:29:09 UTC |
| af0dd8a | Matthias Broecheler | 08 January 2015, 19:48:20 UTC | Fixes #853 | 08 January 2015, 19:48:20 UTC |
| f4291c7 | Matthias Broecheler | 08 January 2015, 19:28:20 UTC | Merge branch 'titan05' of https://github.com/thinkaurelius/titan into titan05 | 08 January 2015, 19:28:20 UTC |
| 4a63653 | Matthias Broecheler | 08 January 2015, 19:25:16 UTC | Fixes #868 | 08 January 2015, 19:25:16 UTC |
| 4ffb0e9 | Matthias Broecheler | 08 January 2015, 18:45:56 UTC | Make index.hostname Maskable so that the hostname can be updated when the external index cluster changes. Fixes #880. | 08 January 2015, 18:45:56 UTC |
| af784bd | Dan LaRocque | 07 January 2015, 13:21:18 UTC | Only apply cache.tx-cache-size min on r/w tx This iterates on a3ea0e5c3cc566984f652619f71b0e058d716909. Read-only transactions can go under the minimum tx-cache-size setting now. Only write-capable transactions are still subject to the minimum. | 07 January 2015, 13:22:45 UTC |
| a3ea0e5 | Dan LaRocque | 07 January 2015, 10:12:30 UTC | Put a min of 100 on cache.tx-cache-size This is a workaround for #893 that's likely to avoid race conditions related to small tx-cache-size values in practice, though it does not technically eliminate the underlying problem. Prior to this commit, I investigated an alternative approach involving WeakReference and a consuming ReferenceQueue drained from the same thread that touches GuavaVertexCache, and that passed Titan's tests appeared to log all the right things via slf4j, but it's still too scary right to introduce so close to a release milestone. The assumption required to make that WeakReference approach work is that dirty vertices are at all times reachable via at least one strong reference *outside* GVC (on any GC root), but it's not completely trivial to prove this for all of Titan's internals. It's also impossible to write a watertight test for the WeakReference approach since its behavior is inextricably linked with GC. | 07 January 2015, 10:13:57 UTC |
| 612ea2d | Dan LaRocque | 07 January 2015, 09:24:12 UTC | Add "args" binding back into ScriptExecutor The Titan ScriptExecutor used to set an "args" variable in the Groovy Binding that pointed to the command-line argument list. The Faunus ScriptExecutor didn't do this. I'm modifying the Faunus ScriptExecutor to set "args" (in addition to the "a1", "a2", ... that it already sets) for backwards-compatibility. This could break existing scripts that explicitly rely on "args" being absent from the variable binding when the script starts, but that seems like an extremely narrow class of scripts. Scripts that first assign to "args" and then do stuff with it should be unaffected. | 07 January 2015, 09:27:15 UTC |
| 4f9ceb0 | Dan LaRocque | 07 January 2015, 09:15:20 UTC | Move argument shift in gremlin.sh This bit of logic has been touched in 018827a538979a93c0b1cd9b4de240e72a235f72 and again in 1b23ce606090eb7e9407e63e26bf8e4e2418ac42, with unintentional regressions in both cases. These options are calling out for automated regression tests. For #903 | 07 January 2015, 09:15:56 UTC |
| 7578354 | Dan LaRocque | 07 January 2015, 07:43:11 UTC | Fix whitespace in graph.set-vertex-id description | 07 January 2015, 07:43:11 UTC |
| da15f29 | Dan LaRocque | 07 January 2015, 07:41:15 UTC | Update links to manual in javadoc comments For #905. This updates the specific outdated URL pointed out by @jaceklaskowski. It also updates several other old wiki URLs turned up by a recursive grep for 'github.*titan/wiki'. | 07 January 2015, 07:41:15 UTC |
| 71325b7 | Stephen Mallette | 05 January 2015, 20:42:32 UTC | Add a note to the docs around Rexster configuration for cassandra to address #908 | 05 January 2015, 20:42:32 UTC |
| 4e38eca | Dan LaRocque | 27 December 2014, 18:43:38 UTC | Removing outdated query precondition This precondition check no longer applies with Contain.IN support, and the underlying invariant it expresses isn't valid anymore. Removing it following discussion with Matthias. For #882 | 27 December 2014, 18:43:38 UTC |
| 5c81611 | Dan LaRocque | 23 December 2014, 16:35:43 UTC | Add failing test with vlabel and Contain.IN conds This is based on #882 | 23 December 2014, 16:36:36 UTC |
| 29491f3 | Dan LaRocque | 22 December 2014, 19:10:45 UTC | Add basic test of ES index creation options This commit adds a test of the new functionality introduced by 6569f8b060a86a6291326e76f5dbe612732b2f7f. For #840 | 22 December 2014, 19:10:45 UTC |
| b08be31 | Dan LaRocque | 19 December 2014, 23:01:04 UTC | Tweak TitanOperationCountingTest expectations This test was broken by de177b9e59b02cd865fb9e49aa4d1a120353ced8 and 03a4c5fb8919d2ff5c0a00c705f0a43818751a95. Updating it to reflect the changes to the way Titan reads schema elements following those changes. | 19 December 2014, 23:03:47 UTC |
| a83e463 | Dan LaRocque | 19 December 2014, 21:18:18 UTC | Add helper method for exception/null-safe rollback This commit introduces a TXUtils.rollbackQuietly which is roughly similar to IOUtils.closeQuietly. This might become obsolete in Titan 0.9 where we can assume try-with-resources and txs are AutoCloseable. First used as part of #881's implementation, but not specifically related to that issue | 19 December 2014, 23:03:47 UTC |
| 9977456 | Dan LaRocque | 19 December 2014, 21:15:40 UTC | Removing tx from SchemaCache method params Now that the SchemaCache.StoreRetrieval implementation constructs a new, cache-disabled transaction for each schema read method invocation, it no longer uses the tx param to its various methods. This lets us remove the tx param from both SchemaCache.StoreRetrieval's methods and SchemaCache's methods. For #881 | 19 December 2014, 23:03:47 UTC |
| e00073c | Dan LaRocque | 19 December 2014, 20:36:09 UTC | Disable cache on correct tx for schema reads de177b9e59b02cd865fb9e49aa4d1a120353ced8 modified StandardTitanGraph.typeCacheRetrieval's retrieveSchemaByName and retrieveSchemaRelations methods to each instantiate a new StandardTitanTx using a key-consistent backend config (i.e. Cassandra QUORUM) inside each retrieve method to perform schema reads. Those methods also disabled cache on a transaction just before the schema reads. However, they disabled cache on the wrong tx -- when I introduced a a new key-consistent tx to these methods for schema reads, I failed to move the disableCache invocation from the old tx to the new key-consistent one. Now cache is disabled on the actual StandardTitanTx used for the schema schema vertex/relation read For #881 | 19 December 2014, 23:03:15 UTC |
| bc88a45 | Dan LaRocque | 18 December 2014, 22:14:32 UTC | Use consistent tx for schema retrieval Experimenting with opening a new transaction with a reference held on the stack solely for the purpose of reading schema vertices and schema relations. For #881 | 19 December 2014, 23:02:25 UTC |
| 24f93bb | Dan LaRocque | 18 December 2014, 14:57:22 UTC | Throw new ExpiredLockException when applicable This commit modifies ConsistentKeyLocker and its superclass to implement the new behavior expected in 6ea5ebf8d0b13c025d08a4734037fb725d0e089c. Previously, a lock that expired while a transaction was holding it would throw a cryptic TemporaryLockingException with the message "No lock columns found for KeyColumn [k=foo, c=bar]". This is not a helpful exception in most cases; the log for ConsistentKeyLocker emits a WARN about the expired lock shortly before this is thrown, but it would be better to have a specific exception type and message to make it clearer about what's happening in this case. Now we have ExpiredLockException. This is a a subclass of TemporaryLockingException. The message string used with it is something like "Expired lock on KeyColumn [k=foo, c=bar]: raw lock timestamp 1418915175000000 MICROSECONDS is older than Duration[300000 ms]". | 18 December 2014, 15:08:16 UTC |
| 6ea5ebf | Dan LaRocque | 18 December 2014, 14:50:15 UTC | Tweak ConsistentKeyLockerTest's expired lock tests This introduces a pair of tests around expired lock behavior: * Check that our own expired locks throw a new ExpiredLockException class when checked * Check that expired locks left behind by other instances, or by the current instance but with a different-than-expected write time, do not necessarily throw an exception in check (unless they prevent the transaction from verifying one or more of its own locks) Previously, only the latter case was implemented and tested. The former case is essentially a special case for #892, wherein we want to provide a more meaningful exception type and message in the event that a transaction's locks expire while held. | 18 December 2014, 14:57:11 UTC |
| bb6a358 | Dan LaRocque | 18 December 2014, 13:54:59 UTC | Minor javadoc improvement on lock status class | 18 December 2014, 13:54:59 UTC |
| 902e80b | Dan LaRocque | 18 December 2014, 13:09:24 UTC | Modify LuceneIndex to support REGEX on STRINGs Lucene (at least at our present version) does not seem to provide a Filter implementation that does regex matching. It does provide a Query implementation for regex matching. LuceneIndex was only built to generate Filters; it always used MatchAllDocsQuery. This change modifies LuceneIndex to allow the convertQuery method to build both a Filter and an accompanying Query. The Lucene REGEX tests introduced in 8f712e70d767313fa4ad401bd295e9bff9fd97bf pass at the moment. For #879 | 18 December 2014, 13:49:31 UTC |
| c298297 | Dan LaRocque | 18 December 2014, 11:22:37 UTC | Enable REGEX tests on Lucene Added a test of Text.REGEX that explicitly specifies Mapping.STRING so that it will activate on Lucene. This commit also makes LuceneIndex report that it supports REGEX, though the implementation just throws an exception right now. The tests are failing. Implementation is up next. For #879 | 18 December 2014, 13:49:31 UTC |
| e306728 | Dan LaRocque | 18 December 2014, 10:55:09 UTC | Deduplicate common ES & Lucene support tests LuceneIndexTest and ElasticSearchIndexTest both implement a testSupport() method that runs assertions on index.supports(...) with a variety of datatypes, mappings, and predicates. Most (but not all) of these testSupport() method bodies were identical between the two test classes. The common segment has been extracted to the shared parent class IndexProviderTest as a new method named testCommonSupport(). This change is intended to simplify upcoming REGEX-related test changes in LuceneIndexTest for #879 | 18 December 2014, 13:49:04 UTC |
| 9d38c24 | Dan LaRocque | 18 December 2014, 08:49:59 UTC | Make Multiplicity/Cardinality explicit in examples For #869 | 18 December 2014, 08:49:59 UTC |
| 50c0998 | Dan LaRocque | 17 December 2014, 17:37:20 UTC | Make Cmp.EQUAL array-aware Array values are now compared with Apache Commons ArrayUtils.isEquals, which is essentially Arrays.equals, but safe for multidimensional arrays. | 17 December 2014, 17:37:20 UTC |
| 2bf1ca3 | Dan LaRocque | 17 December 2014, 17:36:49 UTC | Add test of Cmp.EQUAL with array value This test fails currently For #878 | 17 December 2014, 17:36:49 UTC |
| e911195 | Dan LaRocque | 17 December 2014, 15:37:41 UTC | Add Cardinality & Multiplicity enum shell imports The Cardinality.* and Multiplicity.* enum names are now imported automatically in gremlin.sh and rexster-console.sh as distributed with Titan. For #869 | 17 December 2014, 15:37:41 UTC |
| 1f6f950 | Dan LaRocque | 17 December 2014, 14:24:38 UTC | Support ThreadLocal and CHM for Kryo caching This commit adds the `graph.kryo-instance-cache` option. It takes either the value THREAD_LOCAL (default) or CONCURRENT_HASH_MAP. This commit effectively restores the old Kryo caching behavior of KryoSerializer, where it stored Kryos in a ThreadLocal, and where those ThreadLocals are not necessarily removed when Titan shuts down. The CHM setting provides an alternative that, unlike ThreadLocal, is exposed to synchronization overhead when retrieving cached Kryos, but which also releases all of its cached Kryo references when the graph is shutdown. For #840 | 17 December 2014, 14:24:38 UTC |
| 8d4cb4c | Dan LaRocque | 16 December 2014, 19:49:48 UTC | Tweaking ThreadLocal comment | 16 December 2014, 19:52:08 UTC |
| ab8f6e5 | Dan LaRocque | 16 December 2014, 15:22:31 UTC | AsciiDoc for new ES index creation customization This documents the changes in 6569f8b060a86a6291326e76f5dbe612732b2f7f and f3f79b6120736d30f442f78d59eb62efe8a8d4dd. It doesn't mention the sleep time setting introduced in 979eb87d89bd019f20f82ed6ebf98842a24d3f2c. For #840 | 16 December 2014, 15:22:31 UTC |
| f3f79b6 | Dan LaRocque | 16 December 2014, 14:33:43 UTC | Deleting the ES index creation conf-file option This option was analogous to the client settings conf-file option, except this one controlled settings specific to the request Titan sends to create an index in ES. Not worth adding another conf-file option for this, particularly before the relative-path hack for conf-file options is cleaned up and integrated into the ConfigOption system. For #840 | 16 December 2014, 14:43:58 UTC |
| 6569f8b | Dan LaRocque | 16 December 2014, 14:15:48 UTC | Add ES replica/shard count options This allows the Titan configuration to supply arbitrary key-value settings passed to the Elasticsearch cluster when creating an index during DB bootstrap. This commit reuses the configuration handling code introduced in 304f14e44f986e806ac8e86437ff7b8e46a68045, except this commit controls index creation settings, whereas that prior commit controls client settings. This commit introduces two new config elements: * index.[X].elasticsearch.create.ext (namespace) * index.[X].elasticsearch.create.conf-file (string opt) This commit also changes the option named index.[X].elasticsearch.index-creation-sleep (just introduced in 979eb87d89bd019f20f82ed6ebf98842a24d3f2c) to index.[X].elasticsearch.create.sleep. For #840 | 16 December 2014, 14:20:20 UTC |
| 979eb87 | Dan LaRocque | 16 December 2014, 12:51:01 UTC | add cfg opt for sleep time after ES index creation The Elasticsearch adapter had a hardcoded 200 ms sleep after creating an index. This is now configurable through index.[X].elasticsearch.index-creation-sleep. The default remains unchanged (200 ms). | 16 December 2014, 12:51:01 UTC |
| d42cb26 | Dan LaRocque | 16 December 2014, 12:20:56 UTC | Remove unused field in KryoSerializer c4c72ab3d978f5a5a8515365ecc429fe70215b02 appears to have removed the last use of KryoSerializer's private 'registrations' field. It's not used as of this commit. | 16 December 2014, 12:20:56 UTC |
| 9d1bdc1 | Dan LaRocque | 16 December 2014, 11:46:26 UTC | ThreadLocal cleanup This commit removes ThreadLocal usage from KryoSerializer and CTConnectionFactory. The KryoSerializer ThreadLocal caused problems with Tomcat (#877). CTConnectionFactory's ThreadLocal seems to produce a unmeasurably-small performance gain, if it produces one at all, so I replaced it with an ordinary private final field. | 16 December 2014, 11:46:26 UTC |
| f25f02e | Dan LaRocque | 11 December 2014, 19:57:35 UTC | Disable Faunus type checks when guessing schema FaunusElement does some cardinality/multiplicity integrity checks when adding relations. These are not meaningful when the cardinality/multiplicity of a type is unspecified, such as when reading from N-Triples and writing to SequenceFiles. This commit disables the checks by default. They can be reenabled when writing to a Titan output format, though the checks are not a complete data integrity guarantee when batch-loading is enabled. In particular, it's still possible to violate a uniqueness constraint on a property key when batch-loading is enabled and the Titan-Hadoop schema checks are enabled. | 12 December 2014, 12:02:50 UTC |
| 210efc0 | Dan LaRocque | 10 December 2014, 11:19:07 UTC | Revert "Make Faunus pkeys Cardinality.LIST by default" This reverts commit 70af3f9b5cf9b2811f3aa33aadfec4b51d5aca07. The reverted commit caused a plethora of test failures, all variations on an expected value X in a test method mismatched against the actual value of a-list-containing-X. | 10 December 2014, 11:19:07 UTC |
| 70af3f9 | Dan LaRocque | 10 December 2014, 04:55:28 UTC | Make Faunus pkeys Cardinality.LIST by default These were Cardinality.SINGLE by default before, which maps to Multiplicity.MANY2ONE and could lead to bizarre schema enforcement failures even in workloads that had no explicit schema (such as reading N-Triples and writing SequenceFiles). These keys are now LIST/MULTI by default. | 10 December 2014, 04:55:28 UTC |
| f39fae8 | Dan LaRocque | 26 November 2014, 14:35:07 UTC | Updating some Gremlin snippets in the docs for 0.5 The most important change in this commit is replacement of some Gremlin `(iterable of vertices).type` calls with `(iterable of vertices)*.getVertexLabel()`. I also ran through the getting-started steps in the intro again on 0.5 and copy-pasted the output as it appears today: type=foo no longer appears in `map` output, calling `map` on a single vertex lists each property on a separate line (used to be all on one line enclosed by curly braces apparently), and edge toStrings are formatted slightly differently. The rest of the changes should just account for different vertex IDs than used to be assigned in the getting-started scenario. | 26 November 2014, 14:35:07 UTC |
| 9489245 | Dan LaRocque | 25 November 2014, 20:28:10 UTC | Merge branch 'boorad-titan05' into titan05 | 25 November 2014, 20:28:10 UTC |
| 15b557a | Dan LaRocque | 25 November 2014, 20:21:46 UTC | Merge branch 'titan05' of github.com:boorad/titan into boorad-titan05 | 25 November 2014, 20:21:46 UTC |
| b804fd7 | Dan LaRocque | 25 November 2014, 18:35:42 UTC | Tweak traversal as directed by @dkuppitz New traversal snippet uses the start-dot operator: http://groovy.codehaus.org/Collections#Collections-Gettingefficientwiththestar-dot%27*.%27operator | 25 November 2014, 18:35:42 UTC |
| 6d91a61 | Dan LaRocque | 24 November 2014, 18:18:59 UTC | Add 0.5.2 to compat manifest | 24 November 2014, 18:18:59 UTC |
| 4086937 | Dan LaRocque | 24 November 2014, 18:18:59 UTC | [maven-release-plugin] prepare for next development iteration | 24 November 2014, 18:18:59 UTC |
| 9b6056d | Dan LaRocque | 24 November 2014, 18:18:59 UTC | [maven-release-plugin] prepare release 0.5.2 | 24 November 2014, 18:18:59 UTC |
| e721f73 | Dan LaRocque | 24 November 2014, 18:17:59 UTC | Updating titan.compatible.versions prop | 24 November 2014, 18:17:59 UTC |
| 322b918 | Dan LaRocque | 24 November 2014, 18:14:04 UTC | Add sleep to testIndexQueryWithScore ES rebuilds indexes asynchronously, but testIndexQueryWithScore commits and then immediately tries to search on what was just committed. Maybe we should change the ES test config to force an inefficient full refresh on every write for testing purposes. For now, I'm adding a sleep to the test instead. | 24 November 2014, 18:17:19 UTC |
| ea126c7 | Dan LaRocque | 24 November 2014, 16:49:10 UTC | Merge branch 'issue_808' into titan05 | 24 November 2014, 16:49:10 UTC |
| 2182eb8 | Dan LaRocque | 24 November 2014, 14:10:51 UTC | Set 0.5.2 release date in upgrade instructions | 24 November 2014, 14:10:51 UTC |
| 1e11c64 | Dan LaRocque | 24 November 2014, 14:09:54 UTC | Make release.sh push HTML documentation to S3 | 24 November 2014, 14:09:54 UTC |
| 9fc802d | Dan LaRocque | 24 November 2014, 14:08:52 UTC | Bring release instructions up-to-date | 24 November 2014, 14:09:27 UTC |
| 16f1fae | Dan LaRocque | 24 November 2014, 13:54:47 UTC | Tweak gh-pages-update.sh This script generates a new gh-pages index.html and copies javadocs for the release to /javadoc/$VERSION/ and /javadoc/current/. This commit makes its detection of whether the gh-pages branch already exists more robust by using a git plumbing command instead of checking file existence in the .git directory. Also fix outdated wording talking about wikidoc in one of the messages it prints to console. | 24 November 2014, 13:54:47 UTC |
| 9dcf945 | Dan LaRocque | 24 November 2014, 13:46:38 UTC | READEish file updates for 0.5.2 | 24 November 2014, 13:46:38 UTC |
| 6205f7f | Dan LaRocque | 24 November 2014, 13:23:03 UTC | Remove Maps.immutableEnumMap call For #844. Guava 11 doesn't have this method, so it throws NoSuchMethodError on Hadoop clusters. Changed to ImmutableMaps.copyOf. | 24 November 2014, 13:23:03 UTC |
| 33fe2f0 | Pavel Yaskevich | 24 November 2014, 08:48:41 UTC | use "q=" to set conditions instead of "fq=" for Solr (issue #808) | 24 November 2014, 08:48:41 UTC |
| 34002ea | Dan LaRocque | 23 November 2014, 13:43:39 UTC | Support titan.hadoop.output.location Fix #822 | 23 November 2014, 13:45:08 UTC |
| 66a60a9 | Dan LaRocque | 23 November 2014, 13:42:36 UTC | Adding test of titan.hadoop.output.location For #822. output.location was recently removed and jobdir.location added instead, so this test of output.location currently fails. Reimplementation of the expected (pre-0.5) output.location behavior coming next. | 23 November 2014, 13:44:18 UTC |
| 274af8b | Dan LaRocque | 23 November 2014, 13:13:56 UTC | Merge branch 'titan05' of github.com:thinkaurelius/titan into titan05 | 23 November 2014, 13:13:56 UTC |
| 5a853d7 | Matthias Broecheler | 23 November 2014, 03:03:29 UTC | Support for Contain.IN in queries-centric queries with test coverage. Addresses the second part of #679. Fixes #679. | 23 November 2014, 03:03:29 UTC |
| 8fe79b1 | Matthias Broecheler | 23 November 2014, 00:29:57 UTC | Support for Contain.IN in Vertex-centric queries with test coverage. Addresses the first part of #679 | 23 November 2014, 00:29:57 UTC |
| 8d543a9 | Dan LaRocque | 22 November 2014, 22:27:51 UTC | Fix test excludes in titan-hadoop-parent This change should have been part of 856a84ee55aa106d29db3d6ade540b7ca627dd57 | 22 November 2014, 22:27:51 UTC |
| fb704eb | Matthias Broecheler | 22 November 2014, 04:50:52 UTC | Merge branch 'titan05' of https://github.com/thinkaurelius/titan into titan05 | 22 November 2014, 04:50:52 UTC |
| cfbe4c8 | Matthias Broecheler | 22 November 2014, 04:50:40 UTC | Added a test case to verify that concurrently updating low-selectivity index entries while reading from them causes result duplication because of query limit adjusting. Added configuration option to disable this behavior. Fixes #839 | 22 November 2014, 04:50:40 UTC |
| 90c2cd4 | Dan LaRocque | 21 November 2014, 20:29:38 UTC | Merge branch 'titan05' of github.com:thinkaurelius/titan into titan05 | 21 November 2014, 20:29:38 UTC |
| f8f8204 | Matthias Broecheler | 21 November 2014, 19:39:28 UTC | Fixes #782 and adds some test coverage for VertexList implementations. | 21 November 2014, 19:39:28 UTC |
| 856a84e | Dan LaRocque | 21 November 2014, 19:34:36 UTC | Add test that reads a list-valued prop with Faunus This test is modeled on #807. #807 is reproducible on 0.5.1 but has been fixed in titan05 (0.5.2-SNAPSHOT) at the time of this commit. This was probably fixed as part of earlier Faunus NPE issue fixing, but I haven't bisected and don't know exactly which change did it. This commit adds a test which would catch a regression on #807. | 21 November 2014, 19:34:36 UTC |
| 5e25600 | Matthias Broecheler | 21 November 2014, 19:01:25 UTC | Merge branch 'titan05' of https://github.com/thinkaurelius/titan into titan05 | 21 November 2014, 19:01:25 UTC |
| b9aca32 | Dan LaRocque | 21 November 2014, 18:57:41 UTC | Support Astyanax's setLocalDatacenter option Fixes #841 | 21 November 2014, 18:57:41 UTC |
| 1c37382 | Dan LaRocque | 21 November 2014, 18:55:44 UTC | Make STG's shutdown hook avoid removing itself This is for #842. The shutdown hook now carries out all shutdown steps except hook removal. The shutdown method on STG does everything the hook does plus hook removal. | 21 November 2014, 18:55:44 UTC |
| 018827a | Dan LaRocque | 21 November 2014, 18:45:34 UTC | Fix `gremlin.sh -l <LOGLEVEL>` I inadvertently broke this with 1b23ce606090eb7e9407e63e26bf8e4e2418ac42. Prior to that commit, gremlin.sh passed the "-l FOO" arguments into the Console main class, but the Console main class ignored them. That commit made the Console main class stop ignoring them and try to interpret "-l" as the path to an init file. This commit tweaks gremlin.sh to shift those "-l FOO" arguments off the bottom of the positional parameter set after processing, so that they aren't passed to the Console main class. | 21 November 2014, 18:48:11 UTC |
| d282b99 | Dan LaRocque | 21 November 2014, 17:02:59 UTC | Removing groovy-all from titan-test No longer necessary due to 18f44383dc18968930bac6c36822e0b68012d8c6 | 21 November 2014, 17:02:59 UTC |
| 18f4438 | Dan LaRocque | 21 November 2014, 15:16:51 UTC | Move shaded Groovy + ASM classes to external jar This removes the shaded copy of Groovy 1.8.9 and ASM 3.2 introduced to titan-core in bfcc99dbd71e90f4a2a17b24cf02ab484bf89396. That worked fine in the Maven build, tests, and in Rexster and gremlin.sh testing from the zip archives (in other words, substantially everywhere), but IDEA refused to compile the Groovy classes in this configuration. The Maven build worked; only IDEA failed to build. It seemed to ignore the shade plugin config in titan-core, manually compiling just titan-core/src/main but leaving out the Groovy and ASM classes, resulting in NoClassDefFound on groovy.lang.GroovyObject when building the other modules. It's possible to work around this IDEA limitation by manually adding Groovy 1.8.9 as a global library or as a project library in all the affected modules. IDEA does build the project in that case. But I don't like that approach, since it means IDEA and Maven tests will use different copies of the Groovy runtime. In an attempt to placate IDEA and while trying to keep testing as uniform as possible between Maven and IDEA, I pushed the shaded Groovy + ASM classes out to their own artifact now published to central, named groovy-shaded-asm. This moots IDEA's inability to comprehend the shade plugin config in titan-core, since titan-core is no longer responsible for shading (it's done in this new artifact). This is all related to #784. | 21 November 2014, 15:16:51 UTC |
| de721be | Dan LaRocque | 21 November 2014, 09:12:13 UTC | Add groovy-all titan-test dependency for IDEA This new dependency has scope=provided. Prior to this commit, Maven built the project without error, but IDEA seemed to get confused by some of the changes in #784, and refused to build titan-test with the error message "no groovy library is defined for module". | 21 November 2014, 09:12:13 UTC |
| e9cfca6 | Matthias Broecheler | 21 November 2014, 00:21:51 UTC | Merge branch 'titan05' of https://github.com/thinkaurelius/titan into titan05 | 21 November 2014, 00:21:51 UTC |
| dfb5bea | Matthias Broecheler | 21 November 2014, 00:21:43 UTC | Intermediate commit of test for VertexLists | 21 November 2014, 00:21:43 UTC |
| c3cc603 | Matthias Broecheler | 21 November 2014, 00:20:55 UTC | Fixed java verison in pom | 21 November 2014, 00:20:55 UTC |
| d80c9d8 | Matthias Broecheler | 20 November 2014, 19:56:26 UTC | Fixes #783 | 20 November 2014, 19:56:26 UTC |
| bfcc99d | Dan LaRocque | 20 November 2014, 09:02:44 UTC | Use Groovy 1.8.9 with shaded ASM 3.x This is part of #784. This effectively reverts b1635dcaf0754dcbf1d8dac84e4795b5c6f235ea, which upgraded from Groovy 1.8.9 to 2.3.7. This commit also configures the shade plugin in titan-core to hide Groovy 1.8.9's required copy of ASM 3.x under the package prefix com.thinkaurelius.shaded.groovy.asm. Since the Groovy 1.8.9 classfiles also need to be rewritten to use the shaded package name at every ASM type reference and method callsite, titan-core now includes a copy of Groovy 1.8.9. The package for Groovy's classes is unchanged to maintain compatibility with client code in Rexster and Gremlin-Groovy. Only ASM has moved. Furthermore, this commit adds a new maven-enforcer-plugin execution in the top-level pom. This execution bans dependencies on the ASM 3.x artifacts. ASM 4.x+ is still allowed (since it uses a different groupId than the 3.x series). If this enforcer execution finds an ASM 3.x dep, it will fail the Maven build. | 20 November 2014, 09:02:44 UTC |
| db612b5 | Dan LaRocque | 19 November 2014, 16:07:54 UTC | Remove track-state/paths=true from Hadoop cfgs Grepping recursively for "pipeline.track" in titan-dist/src where the master copies of the example configs live now produces no hits. The defaults for the track-state and track-paths options as defined in TitanHadoopConfiguration also remain false. Fixes #823 | 19 November 2014, 16:07:54 UTC |
| f01d045 | Dan LaRocque | 19 November 2014, 13:55:21 UTC | Making INDEX_DIRECTORY MASKABLE INDEX_DIRECTORY was GLOBAL_OFFLINE prior to this commit. I think MASKABLE will be a relatively safe change for 0.5.2 (LOCAL would not be safe). This should be allowed to vary to support nodes with heterogeneous disk layouts. | 19 November 2014, 13:57:40 UTC |
| 4ba6d1f | Dan LaRocque | 19 November 2014, 13:52:05 UTC | Adding config option for custom MR job classpaths This is related to #800. This commit adds the option "titan.hadoop.mr.classpath-configurer". When present, it's interpreted as the full package.classname of a class implementing JobClasspathConfigurer which has a nullary constructor. This takes precedence over the mapredjar and distcache configurer mechanisms already present in Faunus. | 19 November 2014, 13:52:05 UTC |
| a6e6d75 | Dan LaRocque | 19 November 2014, 13:48:12 UTC | Delete Cassandra data between Expect ITs 8fa00662730ec74089dc4dd604cb247f4dadafa9 introduced a new test, forming a pair of Cassandra tests that could interfere with each other by using the same shared embedded Cassandra instance without dropping data between methods. This adds a @Before that drops those data. | 19 November 2014, 13:48:12 UTC |
| 063d3a3 | Dan LaRocque | 19 November 2014, 13:46:02 UTC | Increasing timeout in Faunus-GraphSON test I've seen this spuriously fail when the machine was under load during the tests. Increasing the timeout. | 19 November 2014, 13:46:02 UTC |
| 8b0a078 | Dan LaRocque | 19 November 2014, 13:44:12 UTC | Fix bug in shorthand argument interpretation a2149cec1d2d9b52b1bad596ef8cb1accdd2f3db broke a static initializer cycle triggered by TitanFactory.open('backend:arg') shorthand invocation, but it also added a bug that broke interpretation the 'arg' part of the shorthand. This is related to #831. | 19 November 2014, 13:44:12 UTC |
| b1635dc | Dan LaRocque | 19 November 2014, 13:25:04 UTC | Attempt upgrade to Groovy 2.3.7 This is part of #784. This commit overrides the Groovy version from 1.8.9 (what TP 2.5.0 compiled against and wants at runtime, but which depends on unshaded ASM 3.x) to 2.3.7, which uses a shaded copy of ASM built with the jarjar utility. This is not ideal. I recompiled gremlin-groovy against 2.3.7 and ran the test suite, which passed, but the Console class required some changes on account of the jline upgrade (1.x to 2.x involved some backwards-incompatible changes to jline's history package). There could be complications here that I'm not seeing yet. | 19 November 2014, 13:43:04 UTC |
| f47ee13 | Dan LaRocque | 19 November 2014, 13:08:37 UTC | Upgrading Avro version This is part of #784. The Avro version managed in the top-level pom prior to this commit, 1.4.1, depended on paranamer, which in turn depended on an unshaded copy of ASM 3.2: [INFO] +- org.apache.hadoop:hadoop-client:jar:2.2.0:compile [INFO] | \- org.apache.hadoop:hadoop-common:jar:2.2.0:compile [INFO] | \- org.apache.avro:avro:jar:1.4.1:compile (version managed from 1.7.4) [INFO] | \- com.thoughtworks.paranamer:paranamer-ant:jar:2.2:compile [INFO] | \- com.thoughtworks.paranamer:paranamer-generator:jar:2.2:compile [INFO] | \- (asm:asm:jar:3.1:compile - version managed from 3.2; omitted for duplicate) This commit updates to Avro 1.7.4, which depends on a different paranamer version that apparently no longer requires unshaded ASM, though I don't know whether that's because paranamer stopped using ASM or whether they've got a shaded and repackaged copy of it somewhere in their artifacts. | 19 November 2014, 13:08:37 UTC |
| e9f5edd | Dan LaRocque | 19 November 2014, 13:04:29 UTC | Update Jersey version from 1.17 to 1.18.2 This is related to #784. 1.17 depends on an unshaded copy of ASM 3.2. 1.18.2 drops the unshaded ASM dependency in favor of carrying its own shaded copy of the ASM classfiles. I'm not certain Rexster will tolerate this. | 19 November 2014, 13:04:29 UTC |
| b48f1e0 | Dan LaRocque | 19 November 2014, 12:45:37 UTC | Cleanup HBase version management The purpose of this commit is twofold: * Centralize HBase version management. The target 0.98.x version was duplicated in several places prior to this commit. Now the top-level pom property ${titan098.core.version} specifies the HBase 0.98 version (without the -hadoop2 suffix), which is appended in ${titan098.version}. * Update to the latest HBase bugfix releases. 0.98 moved from .2 and .3 to .8, and 0.94 moved from .21 to .25. 0.96 does not appear to have new upstream bugfixes and stays at .2. | 19 November 2014, 13:02:08 UTC |
| b4eee85 | Dan LaRocque | 18 November 2014, 18:20:07 UTC | Move Faunus Graph instantiation into RR.initialize I kind of implemented this in 5dd656e050cf1f31580a4425e51b3da272d9bfcb, but I cheated by opening the graph in InputFormat.createRecordReader rather than RecordReader.initialize. I'm not sure whether the contract of createRecordReader makes that safe. This commit moves graph instantiation into RecordReader.initialize in an attempt to remove the uncertainty. Related to #817 | 18 November 2014, 18:22:38 UTC |
| c12d1eb | Dan LaRocque | 18 November 2014, 17:50:45 UTC | Change some github.com urls from master to titan05 This is prompted by #803. I did a grep through all of the docs (recursive) for blob/master and found two hits. A more elegant solution would probably involve an AsciiDoc property that's centrally controlled to avoid repetition, but with only two references, I don't want to go overboard. Changed both to titan05 equivalents and checked that the links were still live. | 18 November 2014, 17:50:45 UTC |
