Member { bind(<>(1, 2, 4, 1, 2) as? Bug21853 - Connection Pool session port connection failure. Previously if the number of CPU cores exceeded the licensed limit, AllegroGraph would generate an error message like the following: This machine exceeds the CPU core count specified in the license. Removed the client-side namespace implementation in favor of a server-side namespace management. Assertionerror: no inf checks were recorded for this optimiser windows. In AllegroGraph WebView when importing statements from a text area input the OK button didn't reenable after the loading process had failed. If the file descriptor limit is raised you'll see a line like the following in just after the server starts: [2016-11-08T17:07:23.
Bug24642: Incorrect text index query warning. The bug would have caused some queries in some datasets to fail to run. Unknown variables in an ORDER BY clause: SELECT * {? Rfe10434 - Rename Lisp API function to duplicate-deletion-strategy. Bug19595 - Repair createGraph() for anonymous graphs.
When using agtool load the error messages signaled while loading triples were truncated. In some cases, the RDFS++ reasoner could follow multiple owl:sameAs paths and generate many duplicate inferred triples. The error was: Fetching user information failed: String table configuration mismatch: Configured number of slots (X) does not match recovered number of slots (Y). RDF/XML serializer can now handle on-the-fly namespace abbreviation, at the cost of more verbose output. If using secondary indices (i. e., UPI-maps), it was possible for Prolog select queries that returned. The following characters are now disallowed in database (repository) names: \ / ~: Space $ {} < > * + [] |. Rfe16639 - Rename agtool command. The number of initial HTTP workers started by the AllegroGraph server used to be exactly the number of backends. Attempts to create repositories in the system catalog will now be met with the following error message: Repositories cannot be created within the 'system' catalog. Previously, agraph-replicate would emit spurious output when exiting. Would return "1", "2" and "3". In order to prevent this, the temporaryFileDiskSpace query option may be set. Assertionerror: no inf checks were recorded for this optimiser referencement. Bug20756 - Multiple OPTIONAL clauses for the same variable could fail. Then the HAVING clause acts like FILTER: SELECT?
True - log information is sent back in the body of the response (using text/plain). 1 CONCAT function could signal an error instead of generating the correct result when one or both of the arguments with a typed literal. You can use a different technique by using the queryAnalysisTechnique query parameter. AdminEmailSMTPHost configuration directive were removed in favor of the new AuditEventsToEmail directive. In each case, the datatype must be specified using its URL. Certain combinations of triple patterns in a BGP and FILTERs could cause AllegroGraph to misapply the FILTERs. Bug23589 - Sending a SPARQL Update command to the Prolog REST API generates a backtrace. Note that aggregation expressions still use the older and slower compiler.