search for: autocommit

I need to turn off and on the autocommit in MySql is there a method in active records that allows me to do this? or is there a method which allows me to type in the pure mysql code "set autocommit=0" Thanks. -- Posted via http://www.ruby-forum.com/.

...olr FTS on dovecot. Read online that some suggested to run cronjob commit every minute, and optimize once a day. I am using Solr 7.1.0 and I see some configurations: In /etc/default/solr.in.sh: #SOLR_OPTS="$SOLR_OPTS -Dsolr.autoSoftCommit.maxTime=3000" #SOLR_OPTS="$SOLR_OPTS -Dsolr.autoCommit.maxTime=60000" Also in solrconfig.xml: ??? <autoCommit> <maxTime>${solr.autoCommit.maxTime:15000}</maxTime> ????? <openSearcher>false</openSearcher> ??? </autoCommit> ?? <autoSoftCommit> <maxTime>${solr.autoSoftCommit.maxTime:-1}</maxTim...

How can I turn autocommit off using my RODBC connection to an Informix database? I want to turn autocommit off, insert a thousand or so rows then commit. I would appreciate any body's input on this.

I''m trying to call save in active record after calling begin_db_transaction. In the code I see no place where it calls commit between create_or_update and the end of save. However in the log I see a commit happen...and I don''t want commit to be called does anyone know how to turn this off? thanks brian

Hello Gluster Community, while reading that article: https://github.com/gluster/glusterfs-specs/blob/master/under_review/worm-compliance.md there seems to be an interesting feature planned for the WORM Xlator: *Scheduled Auto-commit*: Scan Triggered Using timeouts for untouched files. The next scheduled namespace scan will cause the transition. CTR DB via libgfdb can be used to find files that

...be super fast. I'm doing hard commits >every minute via cron so the only consequence of this is that you >cannot search for messages delivered before less then a minute (which >you, usually, don't need to do anyway). > >While googling i also find out that Solr supports autoCommit function >(and from version 4.0 also autoSoftCommit), so there's no reason for >Dovecot to handle this on it's own (and potentially doing hundreds or >thousands of soft commits every second) - you can just set Solr to, >for example, do autoSoftCommit every second and aut...

sorry... I got distracted half way and forgot to put a meaningfull subject so the archive could figure out the thread. - resending. On 4/14/19 4:04 PM, dovecot-request at dovecot.org wrote: >> Solr ships with autoCommit set to 15 seconds and openSearcher set to >> false on the autoCommit.? The autoSoftCommit setting is not enabled by >> default, but depending on how the index was created, Solr might try to >> set autoSoftCommit to 3 seconds ... which is WAY too short. I just run with the default...

...y but just getting things into the index > efficiently, a better approach would be for dovecot plugin not to send > any commit or softCommit (or waitSearcher either) and that should speed > things up. You'd need to configure solr with a long autoSoftCommit > maxTime and a reasonable autoCommit maxTime, which you could then > reconfigure when the load was done. Solr ships with autoCommit set to 15 seconds and openSearcher set to false on the autoCommit. The autoSoftCommit setting is not enabled by default, but depending on how the index was created, Solr might try to set autoSoftC...

...</div> <div> >> any commit or softCommit (or waitSearcher either) and that should speed </div> <div> >> things up. You'd need to configure solr with a long autoSoftCommit </div> <div> >> maxTime and a reasonable autoCommit maxTime, which you could then </div> <div> >> reconfigure when the load was done. </div> <div> > </div> <blockquote type="cite"> <div> Solr ships with autoCommit set to 15 seconds and openSearcher set to...

On 14/04/2019 17:16, Peter Mogensen via dovecot wrote: > sorry... I got distracted half way and forgot to put a meaningfull > subject so the archive could figure out the thread. - resending. > > On 4/14/19 4:04 PM, dovecot-request at dovecot.org wrote: > >>> Solr ships with autoCommit set to 15 seconds and openSearcher set to >>> false on the autoCommit.? The autoSoftCommit setting is not enabled by >>> default, but depending on how the index was created, Solr might try to >>> set autoSoftCommit to 3 seconds ... which is WAY too short. > I just run...

Looking further at tcpdumps of the Dovecot->Solr traffic and Solr metrics it doesn't seem like there's anything suspicious apart from the TCP windows running full and Dovecot backing of ... until it times out and close the connection. >From my understanding of how Dovecot operates towards Solr it will flush ~1000 documents towards Solr in /update request until it has traversed the

...verything started to be super fast. I'm doing hard commits every minute via cron so the only consequence of this is that you cannot search for messages delivered before less then a minute (which you, usually, don't need to do anyway). While googling i also find out that Solr supports autoCommit function (and from version 4.0 also autoSoftCommit), so there's no reason for Dovecot to handle this on it's own (and potentially doing hundreds or thousands of soft commits every second) - you can just set Solr to, for example, do autoSoftCommit every second and autoCommit every mi...

I want to load about 14000 words (a subset of /usr/share/dict/words) into a MySQL table in a migration: class CreateWords < ActiveRecord::Migration def self.up create_table :words, :force => true do |t| t.column :word, :string end say_with_time ''loading words...'' do words = File.join(RAILS_ROOT, ''db'',

On 4/14/19 4:04 PM, dovecot-request at dovecot.org wrote: >> Solr ships with autoCommit set to 15 seconds and openSearcher set to >> false on the autoCommit.? The autoSoftCommit setting is not enabled by >> default, but depending on how the index was created, Solr might try to >> set autoSoftCommit to 3 seconds ... which is WAY too short. I just run with the default...

...ng things into the index >> efficiently, a better approach would be for dovecot plugin not to send >> any commit or softCommit (or waitSearcher either) and that should speed >> things up. You'd need to configure solr with a long autoSoftCommit >> maxTime and a reasonable autoCommit maxTime, which you could then >> reconfigure when the load was done. > > Solr ships with autoCommit set to 15 seconds and openSearcher set to > false on the autoCommit.? The autoSoftCommit setting is not enabled by > default, but depending on how the index was created, Solr might...

...epeat....... However, how can I do this in a block? I have no idea to do so...Please give me some light. all_servers = Server.find(:all) all_servers.each do |s| h = {:host => "localhost", :adapter => "jdbc", :dialect => "sybase", :autocommit => false, :driver => "com.sybase.jdbc3.jdbc.SybDataSource", :url => "jdbc:sybase:Tds:#{s.host):#{s.port}/LOE_DB", :username => "username", :password => "password"} # How to I write code to establish 40 connec...

...http://wiki.rubyonrails.com/rails/pages/HowToUseTransactions: Object2.transaction do Object1.transaction do object1.value1 = "123456" object1.save do_some_error end end - error is produced, but object1 is commited and database is changed - imho transaction is active(autocommit false) only for Object2 connection - ruby-1.8.4, rails-1.0, dbriver is oci any idea about this ? thanks, peter

...ike: :default => Sat Jan 01 00:00:00 Eastern Standard Time 2000. Are there any defaults for built in RDBMS functions such as getdate/sysdate. If not how is that handled? 4) db_schema_dump seems to blow up when ActiveRecord:: Base.connection.instance_variable_get("@connection")["AutoCommit"] = false is not set in environment.rb, however, all other commands don''t work unless AutoCommit is set to true. rake aborted! DBI::DatabaseError: Count OLE error code:8000FFFF in Microsoft OLE DB Provider for SQL Server ITransaction::Commit or ITransaction::Abort was calle...

Hello Group, I have a problem with pending tasks in puppet-dashboard after I set the MySQL parameter autocommit = 0 and sql_mode = TRADITIONAL. Does the dashboard need autocommit to be enabled? Workers are running: env RAILS_ENV=production script/delayed_job status delayed_job: running [pid 4995] delayed_job: running [pid 5019] Regards Kai -- You received this message because you are subscribed...

So with "fts_autoindex=yes" enabled in plugins, is there anything I should be running regularly, other than the expunge/purge, to ensure Solr indexes are updated? I have a daily Solr optimize, and Solr autocommit enabled. I have an hourly "doveadm index -A *" command - is that unneeded? -- Daniel On 4/12/2015 6:53 AM, Timo Sirainen wrote: > On 10 Apr 2015, at 21:55, Daniel Miller <dmiller at amfes.com> wrote: >> Why things happen is one of the great mysteries and joys of being a...