Hight QPS service (poncho-web) is causing an issue that it spilling a log file 1G/0.5 hour. The content of logs comes from querylog in Sensei. We would like to change the logging level from Info to Debug for logging each queries. Qeurylog is useful information for debugging. When we need it, we can enable it through JMX.
…y build and print it when using log.debug!
Added the ability to show the actual query plan during execution. Currently requires uncommenting some code, because logging query plans is expensive. Sensei filters learned to estimate cardinality in order to optimize filter execution order and traverse fewer documents. Specifically, this info is used during ANDs, ORs, and term searches that use facet cache. For ANDs, filters are rearranged so that the lowest-cardinality filters come first, and always-true filters are dropped. For ORs, highest cardinality filters come first, and always-false filters are dropped. Cardinality is tracked as a range (as opposed to Bobo's single-number selectivity), which gives a bit more accurate results.
Conflicts: build.gradle gradle.properties sensei-core/src/main/java/com/senseidb/indexing/DefaultStreamingIndexingManager.java sensei-core/src/main/java/com/senseidb/search/node/SenseiBroker.java sensei-core/src/main/java/com/senseidb/search/node/broker/BrokerConfig.java sensei-core/src/main/java/com/senseidb/servlet/AbstractSenseiClientServlet.java sensei-core/src/test/java/com/senseidb/test/SenseiStarter.java sensei-federated-broker/src/main/java/com/senseidb/federated/broker/proxy/SenseiBrokerProxy.java
if > 0, number of meaningful digits in the fractional part of the score, if < 0, number of digits to discard from the integer part of the score, if == 0, round the score if == null, leave the score intact Example, score=34.461 if scoreMeaningfulDigits=2 then score=34.46, if scoreMeaningfulDigits=-1 then score=30 if scoreMeaningfulDigits=0 then score=34